1 |
On Tue, Jun 13, 2006 at 11:49:58AM +1000, Daniel wrote: |
2 |
> On Sunday 11 June 2006 12:50, Brian Harring wrote: |
3 |
> > On Fri, Jun 09, 2006 at 05:08:23PM -0400, Chris Gianelloni wrote: |
4 |
> > > On Fri, 2006-06-09 at 16:19 -0400, Mike Frysinger wrote: |
5 |
> > > > On Thursday 08 June 2006 21:08, Brian Harring wrote: |
6 |
> > > > > One additional to this- the location for the file in the tree |
7 |
> > > > > *should* be metadata/ - shoving it into profiles is the wrong |
8 |
> > > > > location (it's not profile data, it's repo metadata). |
9 |
> > > > |
10 |
> > > > that is the correct location for it but we have no metadata tree |
11 |
> > > > tracked in cvs |
12 |
> > > |
13 |
> > > How about we keep it where it is (in CVS) and simply have it added to |
14 |
> > > metadata during the normal runs before sync? |
15 |
> > |
16 |
> > Downside to this is that any tool written to expect the file in |
17 |
> > $PORTDIR now doesn't behave as well for cvs users (devs). |
18 |
> |
19 |
> Tools like herdstat use the HERDS environment variable. If other |
20 |
> parsers/users of herds.xml are modified to use the same HERDS then its a |
21 |
> consistant win for cvs users. How many tools are there? |
22 |
> |
23 |
> Once herds.xml gets added to the $PORTDIR/metadata herdstat (and other |
24 |
> programs) will be a lot easier to use for non-devs and budding devs. |
25 |
> |
26 |
> > Either solutions works for me however, mainly after the file being in |
27 |
> > the tree for majority of users. |
28 |
> > ~harring |
29 |
> |
30 |
> I'd be really happy to see it added. Since there really no objection who |
31 |
> controls the staging server enough to implement this? I'm happy to write up a |
32 |
> bug report but I'm not sure who to assign it to. |
33 |
|
34 |
Well, all that's required is modification to rsync gen script; person |
35 |
to bribe is zmedico (maintainer of rsync generation scripts), or your |
36 |
favorite infra monkey. |
37 |
|
38 |
~harring |