While working through another last rites slew, I was thinking that back in the day there were a number of developers who believed they should add a lot of packages to #Gentoo, in the name of giving users a choice. Like, they were projects whose sole purpose of existence seemed to be to find every piece of software that roughly fit a specific topic, get it to build and package it for Gentoo.

Of course, the long-term effect of that is that there's a lot of unmaintained, often broken packages. "The choice" doesn't really work. Sure, users have a lot of packages to choose from — but they have to actually figure out which of these packages are actually useful (if any).

A few years ago attempting to remove packages also faced some verbal opposition. You shouldn't remove unmaintained or outdated packages, because they still work. You shouldn't remove packages that sometimes fail to build, because some flag combinations still work. You shouldn't remove packages that don't build at all, because the user can visit Forums and find some workaround to make them build 🤦. Or they'll have an ebuild handy to start working on it. And anyway, you shouldn't be removing stuff at all, but fixing it instead.

Sometimes the arguments were straight dishonest too: people literally said we need more packages to lure new users in. Like, it didn't matter to them that the packages didn't really work and that the people trying to use them will get a nasty surprise. They wanted people to say "hey, Gentoo has this software we need, let's start using Gentoo".

@mgorny does gentoo have a list of orphaned / unmaintained packages ? void has that and it's nice
Maintainer-Needed – Gentoo Packages

Gentoo Packages Database

@navi @mgorny neat

is there a way to list installed packages with a specific maintainer ? if a package is unmaintained, its users would likely be far better than someone unrelated

otherwise, have a way on update to tell user "hey, you use this package, but it is unmaintained and scheduled for removal, are you willing to maintain it ?"

@SRAZKVT @navi @mgorny

To list orphaned packages (packages with no specific maintainer):

qlist -Iv $(portageq --repo gentoo --orphaned)

@SRAZKVT @navi @mgorny

As someone who does my fair share maintainer-needed drive-bys. There is also a problem with phantom maintainers, so people who bumped a package once and then never showed up again. I feel like pushing this to everyone would just hide the issue again with initially well meaning users rushing in and then forgetting about it.

(Also something being scheduled for removal is already quite loud, as the process involves masking it)

@SRAZKVT @navi @mgorny

Now I may be bit biased due to my own Gentoo habits. But I think it would be better to incentivize more people to fix and bump things they care when its convenient for them rather than pushing for them to become an official maintainer immediately. (+ It would be better onboarding to becoming a maintainer)

I only officially adopt packages once I'm sure I want to keep up to date with its developments and feel comfortable with its possible issues.

@parona @navi @mgorny fair, ig ask them to become maintainer if they did a few updates to the package ?
@mgorny Yeah, the best argument is always "if we have it packaged, it says it's to a reasonably high quality", not "we have a huge selection of crap".
@mgorny Isn't that a good case for having some sort of additional flag, similar to mask, that indicates that a certain repo is out of date/unmaintained/etc. ? Similar to the note that lives at the top of a given package saying that it's out of sync with head ? I know that it's helpful to me when I'm downloading packages to know that they're way out of date and I should probably find something newer/better ...
@mgorny I was in that camp before layman was a thing. These days I'm all for the core portage tree being maintained and high quality, let the rest of the half-broken stuff live in other overlays. They're easy enough to install or work with.