Date: Wed, 19 Dec 2007 19:23:09 +0000 From: Bruce Cran <bruce@cran.org.uk> To: "Aryeh M. Friedman" <aryeh.friedman@gmail.com> Cc: Erich Dollansky <oceanare@pacific.net.sg>, freebsd-questions@freebsd.org Subject: Re: rough method of cleaning the ports tree Message-ID: <47696F9D.3000503@cran.org.uk> In-Reply-To: <47689079.4040700@gmail.com> References: <47688E99.4050802@pacific.net.sg> <47689079.4040700@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Aryeh M. Friedman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > 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 probably want to define NOCLEANDEPENDS so it doesn't try and recursively clean each port - i.e run "make NOCLEANDEPENDS=yes distclean". -- Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47696F9D.3000503>