From: user@example.net   
      
   Arthur Hagen wrote:   
   > J.O. Aho  wrote:   
   >> Aragorn wrote:   
   >>   
   >>>                 - /usr/portage   
   >> Today portage is 3.7G, but that will grow with the number of new   
   >> packages that will be included in future and shrink depending on   
   >> which packages are dropped.   
   >   
   > Today it's not 3.7 GB.  It's around 500 MB (give or take some, based on   
   > the block size of your hard drive), plus whatever you have in   
   > /usr/portage/distfiles (source code and binary packages) and   
   > /usr/portage/packages (compiled packages explicitly saved).   
   > One system here has /usr/portage/distfiles at 14 GB, and that's current   
   > files only (cleaned out nightly with "eclean distfiles"), while another   
   > has it at zero -- just an autofs entry NFS mounting it on demand.   
      
   Yeah, when you say so, I got the whole distfiles included in that size and   
   it's quite a lot of files, as it's shared over NFS and it tends to be that a   
   package which is stable for one architecture is unstable for others, so I have   
   many versions of the source. My distfiles is 2.8G, which would imply that the   
   portage is 0.9G large.   
      
      
   > You can probably get away with less than 1 GB if you zealously clean out   
   > /usr/portage/distfiles between compiles.  If rebuilding world, you can   
   > create a batch job like:   
   >   
   > emerge --color n -pe world | grep ebuild \   
   > | sed -e 's/.*] /emerge -1 =/' -e 's/$/;rm \/usr\/portage\/distfiles\/*/' \   
   > | sh   
      
   or emerge tmpwatch and set it to clean out the directory.   
      
      
      
   --   
      
     //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)