| 1 |
hi ! |
| 2 |
|
| 3 |
> Is there a switch to tell emerge update to not remerge existing packages, |
| 4 |
> but to only emerge newer packages? |
| 5 |
|
| 6 |
afaik, that's not the name of the game, because: |
| 7 |
generic example: |
| 8 |
--package foo is up-to-date |
| 9 |
--package bar gets updated |
| 10 |
--foo depends on bar |
| 11 |
if package foo needs e.g libs from package bar and bar |
| 12 |
gets updated, foo is up-to-date only formally, i.e. the ebuild and |
| 13 |
the sources are, but foo has to be recompiled |
| 14 |
against the libs from bar nevertheless. |
| 15 |
|
| 16 |
> |
| 17 |
> Tom |
| 18 |
|
| 19 |
just my $0.02 |
| 20 |
ciao |
| 21 |
peter |
| 22 |
|
| 23 |
----------------------------------------------------------------- |
| 24 |
Peter Kadau <peterdotkadauatwebdotde> |
| 25 |
|
| 26 |
"Why program by hand in five days what you can |
| 27 |
spend five years of your life automating ?" |
| 28 |
----------------------------------------------------------------- |
| 29 |
_______________________________________________________________________ |
| 30 |
1.000.000 DM gewinnen - kostenlos tippen - http://millionenklick.web.de |
| 31 |
IhrName@×××.de, 8MB Speicher, Verschluesselung - http://freemail.web.de |
Archives