On Mon, Jul 26, 2021 at 3:19 PM Alan Mackenzie <a...@muc.de> wrote:
>
> How would I track down the Gentoo maintainer?
>

So, first thing to do is look in the repository at the metadata.xml
file in the package directory.

In this case it only lists the base-system project and doesn't list
any individual maintainers.  You could try looking up the project on
the wiki:
https://wiki.gentoo.org/wiki/Project:Base

However, you're going to find a lot of people.  You could email the
email address on the wiki page, or try asking in that project IRC
channel.

If that doesn't get you far (these sorts of projects often are a
little disorganized since there are so many packages in them), then
I'd look at the commit history:
https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-process/daemontools

(or you can run git whatchanged . from inside that directory in a git clone)

My first guess of an individual to talk to would be sam@g.o, since he
has done commits related to the actual package itself looking at the
log.  Things like stabilization commits or people touching a package
because they were working on something somewhat related aren't ideal
contacts, since they probably aren't directly involved with the
package.

If you're on IRC I'd check out #base-system there though, and maybe
ask in general or ping sam if he's around.

I realize this is a bit roundabout, but one thing I do want to do is
teach you to fish, and also make you not too afraid to talk to a
package maintainer.  The trick is to find the person who is most
likely to care about the issue because they're most likely to identify
the right sort of fix.

If you get really stuck please do let me know and I can try to help a
bit.  The more I heard on this the more I tend to think that maybe it
should either not be in that virtual or that it should itself depend
on openrc/etc, or that qmail shouldn't depend on it.  However, I am
not directly involved in those packages and there could be more to the
story.  That is why it is good to talk to those directly involved.

-- 
Rich

Reply via email to