I was searching a bit through bugzilla for some ebuilds for programs,
that are not yet in portage and I found, there are a lot of programs
hanging in buzilla, because no one did take them for maintenance.
Now some of them are quite old (no comments/activity for 2 years) and I
tried some of them and found out, that sometimes they don't even
Now I was wondering, if there is a standard procedure for things
like this; I searched the mailing list for sth. like this, but didn't find
So my question is, is there some kind of standard procedure for old
ebuilds that lay around bugzilla, and if not, maybe there should be one?
I was thinking about something like this:
- Categorize ebuild requests, so one category should contain the programs,
that aren't developed anymore, one category those, that are still developed,
but won't work with a current toolchain/system, and those programs, that
will still work with current systems.
- Add them to some kind of tracker, so some users that are up to it can try
to fix them, and report that, and if it not fixable, resolve the bugs as
- Maybe make use of the vote system, so bugs with ebuilds, that are
and don't have votes, will be closed after something like 2 years with no
activity (but that would include to tell users, that they have to vote).
Maybe there are better ways handling this.
But I think, there is at least a problem with the number of "dead" ebuilds
in bugzilla, because I think, that at least those, that will still work
firstname.lastname@example.org mailing list
12-26-2007, 03:38 PM
Old ebuilds in bugzilla
Raised that a month or two ago here, conclusion:
If you find something dead, just ping someone with appropriate rights to
When you care about that pkg, either find a maintainer for it or take it
up to sunrise overlay yourself.