From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] missing <herd> tag in metadata.xml
Date: Thu, 10 May 2007 19:38:13 +0200 [thread overview]
Message-ID: <200705101938.16111.bangert@gentoo.org> (raw)
In-Reply-To: <46433E31.4070107@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
> >
> > Is it reasonable to simply add the <herd>no-herd</herd> or should
> > perhaps the policy be relaxed, such that a missing <herd> tag is
> > equivalent with <herd>no-herd</herd>?
>
> iirc there was a flamewar about this a while ago. you should look at
> the archives to see what people decided.
whatever the outcome of the discussion was, the current situation is still
unclear, which is why it needs to be addressed again.
either we decide to relax the policy and change the documentation, or we
dont and fix the ebuilds.
/me goes back to reading up on some history:
The Dreaded herd tag - 2006-10-28
http://thread.gmane.org/gmane.linux.gentoo.devel/43733
Herds suck, fix them - 2006-06-15
http://thread.gmane.org/gmane.linux.gentoo.devel/39385
Please use land-misc herd where appropriate! No no-herd madness!!!
2004-10-07
http://thread.gmane.org/gmane.linux.gentoo.devel/21899
Packages with non-existent herd in metadata.xml - 2004-09-27
http://thread.gmane.org/gmane.linux.gentoo.devel/21633
kind regards
Thilo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-10 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 15:38 [gentoo-dev] [RFC] missing <herd> tag in metadata.xml Thilo Bangert
2007-05-10 15:45 ` Mike Doty
2007-05-10 17:38 ` Thilo Bangert [this message]
2007-05-10 20:11 ` Bo Ørsted Andresen
2007-05-11 1:05 ` Thilo Bangert
2007-05-11 20:57 ` [gentoo-dev] " Ryan Hill
2007-05-12 14:26 ` [gentoo-dev] " Thilo Bangert
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=200705101938.16111.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