Mailing List Archive

On 6/9/06, Grant Goodyear <g2boojum@gentoo.org> wrote:
> So, what would people think of moving herds.xml from gentoo/misc into
> the portage tree, with the rationale being that local tools could use
> that information for various useful purposes (compiling statistics,
> doing something that I can't think of right now, whatever)?
>

How exactly would that be performed and what negative effects would
the change produce?


--
Ioannis Aslanidis

<deathwing00[at]gentoo.org> 0xB9B11F4E
--
gentoo-dev@gentoo.org mailing list

On 6/9/06, Grant Goodyear <g2boojum@gentoo.org> wrote:
> So, what would people think of moving herds.xml from gentoo/misc into
> the portage tree, with the rationale being that local tools could use
> that information for various useful purposes (compiling statistics,
> doing something that I can't think of right now, whatever)?
>

How exactly would that be performed and what negative effects would
the change produce?


--
Ioannis Aslanidis

<deathwing00[at]gentoo.org> 0xB9B11F4E
--
gentoo-dev@gentoo.org mailing list

On Fri, Jun 09, 2006 at 02:54:08AM +0200, Ioannis Aslanidis wrote:
> On 6/9/06, Grant Goodyear <g2boojum@gentoo.org> wrote:
> >So, what would people think of moving herds.xml from gentoo/misc into
> >the portage tree, with the rationale being that local tools could use
> >that information for various useful purposes (compiling statistics,
> >doing something that I can't think of right now, whatever)?
> >
>
> How exactly would that be performed and what negative effects would
> the change produce?

Couple of ways- either
1) actual cvs move of the file. Changes required are updating any
scripts relying on the existing cvs location (namely
http://www.gentoo.org/proj/en/metastructure/herds/herds.xml)
2) placing a copy of the file in the rsync image. Downside, any tool
reliant on herds.xml being in the tree will not behave perfectly for
cvs users (they don't get the metadata directory typically).

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).
~harring

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
-mike

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?

--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

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).

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

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

On Tue, Jun 13, 2006 at 11:49:58AM +1000, Daniel wrote:
> 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.

Well, all that's required is modification to rsync gen script; person
to bribe is zmedico (maintainer of rsync generation scripts), or your
favorite infra monkey.

~harring

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian Harring wrote:
> Well, all that's required is modification to rsync gen script;

I'll do it, assuming that a location has been agreed upon. $PORTDIR/metadata/herds.xml is the place?

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEjkP7/ejvha5XGaMRAgTZAJ9csOH4y7/A3fcMvh0exGrE9GHjzACg6vDl
3QUXrniKhWLyhIupyap/tMc=
=SGau
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list

On Friday 09 June 2006 03:08, Brian Harring wrote:
> On Fri, Jun 09, 2006 at 02:54:08AM +0200, Ioannis Aslanidis wrote:
> > On 6/9/06, Grant Goodyear <g2boojum@gentoo.org> wrote:
> > >So, what would people think of moving herds.xml from gentoo/misc into
> > >the portage tree, with the rationale being that local tools could use
> > >that information for various useful purposes (compiling statistics,
> > >doing something that I can't think of right now, whatever)?
> >
> > How exactly would that be performed and what negative effects would
> > the change produce?
>
> Couple of ways- either
> 1) actual cvs move of the file. Changes required are updating any
> scripts relying on the existing cvs location (namely
> http://www.gentoo.org/proj/en/metastructure/herds/herds.xml)

That one will have to be changed anyway. It runs on my office system, and my
job ends at the end of the month.

I don't have any particular problem with things. Perhaps though we should do
the copying the herds file into the web tree different anyway.

Paul

--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net