Adding to your list of reasons are: gcc/glibc upgrades have in the past required a full system recompile from scratch: this happened for gcc 2.95 to 3.0, 3.1 (and 3.2?) and looks like it will soon be neccessary with 3.3 if you want to get the advertised gains.
change of opt flags in make.conf and you then need to recompile the system to enable them in each lib/binary a -rn version upgrade by portage usually just patches, or changes the configuration in the ebuild so the downloaded tarball is reused (e.g., setting permissions on some file that escaped the first iteration) - happens often! That being said, it would be nice if the glag was 0,1,3,... so you could keep 0 versions (need space), 1 version (whats installed), 2 (whats installed, and prev in case you need to roll back). You could then use 0 for a laptop, and 2 for a server etc. BillK On Tue, 2003-09-23 at 19:52, [EMAIL PROTECTED] wrote: > > > Have I missed something again? > > Is there really no option or flag or feature or something to set in > /etc/make.conf so that emerge will remove the /usr/portage/distfiles/* that > were downloaded for the installation? > > In my situation I don't see why I would ever re-install something already > installed. > > I can see the advantage for developers installing the same packages several > times. > I can also see the potential interest for someone being on a slow line with > mucho harddisk. > -- [EMAIL PROTECTED] mailing list
