public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel <dragonheart@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] herds.xml
Date: Tue, 13 Jun 2006 11:49:58 +1000	[thread overview]
Message-ID: <200606131149.59676.dragonheart@gentoo.org> (raw)
In-Reply-To: <20060611025026.GA12419@nightcrawler>

[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]

On Sunday 11 June 2006 12:50, Brian Harring wrote:
> On Fri, Jun 09, 2006 at 05:08:23PM -0400, Chris Gianelloni wrote:
> > On Fri, 2006-06-09 at 16:19 -0400, Mike Frysinger wrote:
> > > On Thursday 08 June 2006 21:08, Brian Harring wrote:
> > > > One additional to this- the location for the file in the tree
> > > > *should* be metadata/ - shoving it into profiles is the wrong
> > > > location (it's not profile data, it's repo metadata).
> > >
> > > that is the correct location for it but we have no metadata tree
> > > tracked in cvs
> >
> > How about we keep it where it is (in CVS) and simply have it added to
> > metadata during the normal runs before sync?
>
> Downside to this is that any tool written to expect the file in
> $PORTDIR now doesn't behave as well for cvs users (devs).

Tools like herdstat  use the HERDS environment variable. If other 
parsers/users of herds.xml are modified to use the same HERDS then its a 
consistant win for cvs users. How many tools are there?

Once herds.xml gets added to the $PORTDIR/metadata herdstat (and other 
programs) will be a lot easier to use for non-devs and budding devs.

> Either solutions works for me however, mainly after the file being in
> the tree for majority of users.
> ~harring

I'd be really happy to see it added. Since there really no objection who 
controls the staging server enough to implement this? I'm happy to write up a 
bug report but I'm not sure who to assign it to.

-- 
Daniel Black <dragonheart@gentoo.org>
Gentoo Crypto/dev-embedded/Forensics/NetMon

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2006-06-13  1:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 23:23 [gentoo-dev] herds.xml Grant Goodyear
2006-06-09  0:54 ` Ioannis Aslanidis
2006-06-09  0:54   ` Ioannis Aslanidis
2006-06-09  1:08   ` Brian Harring
2006-06-09 20:19     ` Mike Frysinger
2006-06-09 21:08       ` Chris Gianelloni
2006-06-11  2:50         ` Brian Harring
2006-06-13  1:49           ` Daniel [this message]
2006-06-13  4:27             ` Brian Harring
2006-06-13  4:50               ` Zac Medico
2006-06-15 20:43     ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2003-09-19  9:33 [gentoo-dev] Herds.xml Philippe Lafoucrière
2003-09-19 21:06 ` Paul de Vrieze
2003-09-20  7:22   ` Philippe Lafoucrière

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=200606131149.59676.dragonheart@gentoo.org \
    --to=dragonheart@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