| 1 |
On Wed, 20 Oct 2004, Tim Cera wrote: |
| 2 |
|
| 3 |
> I submitted a patch (a long time ago) that only rsynced the portage |
| 4 |
> tree for the installed ebuilds. Worked great. Would have to be |
| 5 |
> extended to fetch new ebuilds when USE variables or dependencies |
| 6 |
> change. |
| 7 |
> |
| 8 |
> http://bugs.gentoo.org/show_bug.cgi?id=44526 |
| 9 |
> |
| 10 |
> A really cool benefit would be that you could collect what people installed |
| 11 |
> from the rsync server logs. |
| 12 |
|
| 13 |
I'd also like it to be extended so that it could also sync an additional |
| 14 |
watchlist of packages. The main purpose of this is, "I'm planning on |
| 15 |
installing Foo on Saturday. I want my portage to be up to date before I |
| 16 |
start the install, but I don't want to sync twice in 24 hours, nor do I |
| 17 |
want to sync every package." Of course, since one could simply sync the |
| 18 |
full set, possibly minus a hand-crafted excludefrom list, this is a much |
| 19 |
lesser item. |
| 20 |
|
| 21 |
I'm impressed; it applied cleanly after all this time (offset 334 |
| 22 |
lines on the second chunk.) |
| 23 |
|
| 24 |
Personally, I don't think that the rsync logs would be that significant. |
| 25 |
If I did, I wouldn't contemplate using this option. Of course, I'm |
| 26 |
assuming a watch list, which would throw a certain amount of very needed |
| 27 |
sand into those stats. |
| 28 |
|
| 29 |
Ed |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives