View previous topic :: View next topic |
Author |
Message |
curmudgeon Veteran
Joined: 08 Aug 2003 Posts: 1740
|
Posted: Thu Feb 19, 2004 11:03 pm Post subject: /var/tmp/portage |
|
|
I just had an ebuild blow up after more than twenty-four hours
of compiling because it ran out of space on /var (a separate
filesystem). It ran out of space because remnants of past (failed)
ebuilds still haunted the system (about 3.5 GB worth when I
added them up).
Questions:
1. Do these directories and files have any value after a (successful)
ebuild, or can I just alias emerge to a script that calls the emerge
program, and then does an "rm -fr /var/tmp/portage" after the
program finishes (with an error code of 0).
2. Does portage have any options to clean this up. Simply removing
all of the directories from packages no longer on the system would
represent a huge step in the right direction, but an option to remove
them as part of the ebuild process (especially after, say, upgrading
to a new version of a package) seems even better. |
|
Back to top |
|
|
ecatmur Advocate
Joined: 20 Oct 2003 Posts: 3595 Location: Edinburgh
|
Posted: Thu Feb 19, 2004 11:36 pm Post subject: |
|
|
Unless you have FEATURES="noclean" Portage will delete almost everything in /var/tmp/portage/pkgspec after a successful merge. Your plan could work except it would cause problems when doing merges during an ebuild post-mortem. If you think that won't be a problem, then go for it; personally I rely on remembering to houseclean that area every few weeks or so. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|