Date: Thu, 20 Dec 2007 00:34:24 +0800 From: Erich Dollansky <oceanare@pacific.net.sg> To: Jerry McAllister <jerrymc@msu.edu> Cc: "Aryeh M. Friedman" <aryeh.friedman@gmail.com>, freebsd-questions@freebsd.org Subject: Re: rough method of cleaning the ports tree Message-ID: <47694810.6020106@pacific.net.sg> In-Reply-To: <20071219162002.GB45237@gizmo.acns.msu.edu> References: <47688E99.4050802@pacific.net.sg> <47689079.4040700@gmail.com> <20071219162002.GB45237@gizmo.acns.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Jerry McAllister wrote: > On Tue, Dec 18, 2007 at 10:31:05PM -0500, Aryeh M. Friedman wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Erich Dollansky wrote: >>> 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) > > That's a good idea too. > But, it might not do enough. So, still consider moving /usr/ports. > it does what I really want. I do not have a space problem. I simply want to get rid of the stuff which is not really needed. A make clean takes to long. Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47694810.6020106>