| 1 |
On Fri, Sep 01, 2006 at 09:54:09PM -0700, Daniel Ostrow wrote: |
| 2 |
> <snip> |
| 3 |
> |
| 4 |
> > > I like this option better than sticking another file into the public |
| 5 |
> > > tree that no user will ever need. |
| 6 |
> > |
| 7 |
> > Instead, modifying the eclass metadata and adding two new keys, that |
| 8 |
> > users will never need is fine? :) |
| 9 |
> > |
| 10 |
> > This isn't really user data, tiz developer data; thus the user bit |
| 11 |
> > doesn't matter. Sarcasm aside, what *does* matter as that the |
| 12 |
> > purpose of this is a temporary hack to cover portages ass. |
| 13 |
> </snip> |
| 14 |
> |
| 15 |
> In light of it being useless data for users is there any reason not to |
| 16 |
> add the files to CVS and then pull them out before the tree is synced |
| 17 |
> with the master mirror as part of that script? |
| 18 |
|
| 19 |
Devs are lazy and don't always do a full cvs up, same reason the |
| 20 |
repoman metadata.xml check relies on pulling metadata.dtd down, |
| 21 |
instead of having a copy pushed into the cvs repository. |
| 22 |
|
| 23 |
Re: yoinking the file from the cvs->rsync transfer, frankly who cares. |
| 24 |
It's one file out of 124 _thousand_ files; <400 bytes. Really ain't |
| 25 |
worth it. |
| 26 |
|
| 27 |
~brian |
Archives