From: Weeve <weeve@gentoo.org>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] ANNOUNCEMENT: metadata.xml files can be created
Date: Wed, 2 Jul 2003 15:00:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307021459170.7212@stargazer.weeve.org> (raw)
In-Reply-To: <200307022034.40019.pauldv@gentoo.org>
On Wed, 2 Jul 2003, Paul de Vrieze wrote:
> On Wednesday 02 July 2003 20:26, Weeve wrote:
> >
> > OK cool. Now for the next question. If I add a metadata.xml file to a
> > package I maintain, leaving the herd as no-herd (using skel.metadata.xml
> > as a template), does this cause anything to break?
>
> It currently does not break anything, but it is not supposed to contain
> no-herd. I think though that it containing no-herd is better than it
> containing an empty tag. Basically the herd needs to be assigned.
So what we need(ed) to do first is/was come up with the herds before we
start asking package maintainers to add metadata.xml files to their
packages?
--
Weeve
Gentoo/Sparc Team Lead
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-02 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 13:36 [gentoo-dev] ANNOUNCEMENT: metadata.xml files can be created Paul de Vrieze
2003-07-02 13:53 ` [gentoo-dev] Re: [gentoo-core] " Weeve
2003-07-02 13:53 ` [gentoo-dev] " Paul de Vrieze
[not found] ` <200307021558.28276.pauldv@gentoo.org>
[not found] ` <20030702140148.GA7822@zaphod.anachem.ruhr-uni-bochum.de>
2003-07-02 14:03 ` [gentoo-dev] Re: [gentoo-core] " Paul de Vrieze
2003-07-02 14:56 ` Aron Griffis
2003-07-02 14:23 ` [gentoo-dev] " Paul de Vrieze
2003-07-02 17:03 ` [gentoo-dev] Re: [gentoo-core] " Weeve
2003-07-02 17:19 ` Weeve
2003-07-02 17:24 ` Weeve
2003-07-02 18:19 ` Paul de Vrieze
2003-07-02 18:26 ` Weeve
2003-07-02 18:34 ` Paul de Vrieze
2003-07-02 19:00 ` Weeve [this message]
2003-07-02 20:44 ` Paul de Vrieze
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=Pine.LNX.4.53.0307021459170.7212@stargazer.weeve.org \
--to=weeve@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=pauldv@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