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
pgpUFlPLs4dz7.pgp
Description: PGP signature
