rough method of cleaning the ports tree

Bruce Cran bruce at
Wed Dec 19 11:23:13 PST 2007

Aryeh M. Friedman wrote:
> Hash: SHA1
> Erich Dollansky wrote:
>> Hi,
>> after noticing how large my ports tree grows while compiling, I
>> thought of simply deleting it and do a CVSup to get a new one after
>> the compilation is finished.
>> This should be much faster and also should do some kind o
>> defragmentation. I simply cannot believe that the huge ports tree
>> will still be very well organised after some months.
>> What does the list think of this method?
> Even though it will take quite a bit longer you should just do a "make
> distclean" in /usr/ports that way anything you hand modified will be
> retained (also you might want to consider keeping a local cvs
> repository if this is an issue)

If you're running a "make [dist]clean" from the top-level directory you 
want to define NOCLEANDEPENDS so it doesn't try and recursively clean each
port - i.e run "make NOCLEANDEPENDS=yes distclean".


More information about the freebsd-questions mailing list