It can be somewhat difficult to find someone to look over and commit an
ebuild on an unmaintained package though - the several times i've done that
have involved tracking down developers with previous commits to the package
or who are active in the category and trying to find one who isn't retired
(I have good taste in packages, apparently - high turnover :P). On one, I
had to talk to 7 different developers before I found someone willing and
able to help. Just adding to the bug probably won't help unless it's
assigned to someone - take a look at it's changelog
(/usr/portage/category/package/Changelog) and try to get in touch with
specific people if nobody responds to the tracker.

Random idea: How about a different bug assignee for maintainer-needed
packages with provided ebuilds/patches? Either something generic, or try to
go for something more category/package specific (herds, etc). Lots of work
for bugwranglers, though. There is a huge difference to developers between
an unmaintained package with no progress and just looking over an ebuild
that has been used successfully by several people.

- John Brooks

On Sat, Aug 16, 2008 at 2:18 PM, Robert Bridge <[EMAIL PROTECTED]> wrote:

> On Sat, 16 Aug 2008 18:42:35 +0200
> Aniruddha <[EMAIL PROTECTED]> wrote:
> > I've filed the bugreport (version bump) a year ago. It looks like borg
> > has no maintainer.
> So maintain it. You don't need to be a dev to write an ebuild, and
> there are enough devs who are happy to throw an eye over user donated
> ebuilds and commit them to the tree...
> Removing a package from portage simply because no one has commited the
> up-to-date version you want is silly. If the only problem is
> no version bumping, provide the ebuild. Someone will commit it. I've
> done that for a few packages, it's not hard.
> I don't know anything about borg specifically, but as a user, I would
> not want to see packages being removed from portage just because the
> devs are too busy to write version bump ebuilds.
> Rob.

Reply via email to