Thilo Bangert wrote:
Doug Goldstein <[EMAIL PROTECTED]> said:
Thilo Bangert wrote:
All packages with <herd>maintainer-needed</herd> will be moved to
<herd>no-herd</herd>.
maintainer-needed is different from no-herd. no-herd is valid when a
dev is maintaining a pkg outside of a herd. no-herd is not valid for
when the package is entirely unmaintained, maintainer-needed would be a
better tag for it. I would not make that change.
if that were so, we would need to document it.
from my reading of the current policies[1,2,3] <herd> is required and
either no-herd or in herds.xml, no-herd only being allowed if no herd
fits.
This is where all the discussions died from last time, that I can tell. We
never really decided on a specific policy change, and nothing got documented, or
done.
In the end, we still have a few ebuilds in the tree that have no maintainer or
no herd, and nobody really cares since all the portage utilities work around it
anyway.
Still, as a matter of QA, it'd be nice to fix.
Steve
--
[EMAIL PROTECTED] mailing list
