1 |
On Tue, 2004-07-27 at 10:23, Blue Cantral wrote: |
2 |
> Re the amount of files involved in rsync. There is a script |
3 |
> floating around the forum making use of the exclude |
4 |
> function of rsync. This reduced the amount of files in my |
5 |
> average rsync to well under a quarter. Very nice little |
6 |
> script :p As soon as I get to a pc I'll look and send a |
7 |
> link. |
8 |
I think I might have been one of the peeps who tore into that script a |
9 |
bit- I view it akin to morphine, yeah, it makes things seem so much |
10 |
better, but sooner or later long term usage will blow out your liver and |
11 |
then your screwed. :-) |
12 |
|
13 |
Excluding portions of the tree for rsync is potentially quite dangerous- |
14 |
dev's w/ cvs access likely have seen this, if you aren't updating the |
15 |
*entire* tree, sooner or later a package creeps in that has a dep that |
16 |
cannot be satisfied by the user's local multi-version repository. |
17 |
|
18 |
The problem w/ most exclude attempts is that to limit the sync to just |
19 |
the installed packages, you're not checking out potential deps. Fex, |
20 |
you've emerged mplayer, but never had the aalib flag on. You decide you |
21 |
want to watch your files using the ascii video extension, flip on |
22 |
USE="aalib", and emerge mplayer. |
23 |
|
24 |
If you've been using the exclude script, and don't have aalib installed, |
25 |
your mplayer is built against the version you had when you decided |
26 |
syncing the whole tree was a pita- instead of version 1.0, you end up w/ |
27 |
the first import of the ebuild, 0.1 (as an example). |
28 |
|
29 |
Another example, you've never installed rzip (nifty compressor), and |
30 |
decide to take it for a spin. If you've been using the rsync exclude |
31 |
for any length of time, your rsync ebuilds are now *way* behind what the |
32 |
tree currently has. You're emerging an older version, that may not even |
33 |
be in the tree anymore. |
34 |
|
35 |
Last time this was brought up, it was pointed out that you could just go |
36 |
and resync the package you're about to emerge. This doesn't work |
37 |
incredibly well, since you have to sync the deps also. |
38 |
~brian |