From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] invalid <herd> in metadata.xml
Date: Fri, 11 May 2007 00:27:32 +0200 [thread overview]
Message-ID: <200705110027.36255.bangert@gentoo.org> (raw)
In-Reply-To: <46437287.4060106@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Doug Goldstein <cardoe@gentoo.org> 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.
>
> I tried to fix up your list and
thanks
> found a handful of the packages not
> even in existence in the tree. Can you re-run this with a fully up to
> date tree?
funny - so why would cvs up not be enough? which packages? i was able to
find all packages on packages.gentoo.org
thanks
[1]http://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/index.html
[2]http://www.gentoo.org/proj/en/metastructure/herds/index.xml
[3]http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-10 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 14:55 [gentoo-dev] invalid <herd> in metadata.xml Thilo Bangert
2007-05-10 15:56 ` Steve Dibb
2007-05-10 19:29 ` Doug Goldstein
2007-05-10 22:27 ` Thilo Bangert [this message]
2007-05-11 1:22 ` Steve Dibb
2007-05-11 15:36 ` Mike Frysinger
2007-05-11 22:52 ` Thilo Bangert
2007-05-10 20:00 ` [gentoo-dev] " Stefan Schweizer
2007-05-11 20:48 ` Ryan Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200705110027.36255.bangert@gentoo.org \
--to=bangert@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox