| 1 |
On Wed, 2004-04-14, 23:36:24 +0300, in <407DA0C8.9050507@××.ro>, |
| 2 |
KRimminal <krimminal@××.ro> wrote: |
| 3 |
|
| 4 |
[snip] |
| 5 |
> i wasn't talking about the unused ones, just the ones that have newer |
| 6 |
> downloaded releases. like portage-1-2-3-4 would be replaced by |
| 7 |
> portage-2-3-4-5 thus making portage-1-2-3-4 obsolete, and so, a |
| 8 |
> clutter. |
| 9 |
|
| 10 |
Random thoughts: |
| 11 |
|
| 12 |
1. When updating a package, say from foo-1.2 to foo-2.3, move the |
| 13 |
sources for foo-1.2 from $DISTDIR to $DISTDIR/old. Portage can still |
| 14 |
find the sources (once it's updated to look in $DISTDIR/old also), but |
| 15 |
can be manually scrubbed. |
| 16 |
|
| 17 |
2. Change ebuild.sh so that it "installs" the sources in $DISTDIR. When |
| 18 |
packages are unmerged and/or updated, the cruft will vanish. Those who |
| 19 |
dislike that behavior can add $DISTDIR to their CONFIG_PROTECT. Even a |
| 20 |
cfg-protected distdir would be easier to maintain. |
| 21 |
|
| 22 |
bash-2.05b$ equery belongs /usr/portage/distfiles/foo-2.3.tbz2 |
| 23 |
Searching for '/usr/portage/distfiles/foo-2.3.tbz2'... |
| 24 |
sys-misc/foo-2.3 (/usr/portage/distfiles/foo-2.3.tbz2) |
| 25 |
bash-2.05b$ equery belongs /usr/portage/distfiles/foo-1.2.tbz2 |
| 26 |
Searching for '/usr/portage/distfiles/foo-1.2.tbz2'... |
| 27 |
bash-2.05b$ |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Batou: Hey, Major... You ever hear of "human rights"? |
| 32 |
Kusanagi: I understand the concept, but I've never seen it in action. |
| 33 |
--Ghost in the Shell |
Archives