Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!uunet!in1.uu.net!news.u.washington.edu!mac-pal.apl.washington.edu!user From: kargl@apl.washington.edu (steve) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: correct use of ports ? Date: Tue, 11 Jul 1995 09:50:16 -0800 Organization: University of Washington Lines: 34 Message-ID: <kargl-1107950950160001@mac-pal.apl.washington.edu> References: <3tsc4r$5g5@stang.netspace.net.au> <kargl-1007951755090001@mac-pal.apl.washington.edu> <3tslkf$kaj@agate.berkeley.edu> NNTP-Posting-Host: mac-pal.apl.washington.edu In article <3tslkf$kaj@agate.berkeley.edu>, jkh@violet.berkeley.edu (Jordan K. Hubbard) wrote: > In article <kargl-1007951755090001@mac-pal.apl.washington.edu>, > steve <kargl@apl.washington.edu> wrote: > >After you install the port, you can delete the source files; ie > > > >%rm -rf /path/to/port_dir > > This is actually a bad idea since you'd delete all the meta files > for the port itself in addition to the `extracted' copy. Just make > install to install the port, make clean to clean up after the > build and, if you ever decide you wish to get rid of the installed > copy later, use pkg_delete to delete it. Don't just go removing > files with rm! In the case of both the ports's data files AND the > resulting port that it installs, some other utilities are keeping > track of them and should be used for any removal operation. If you > don't want to fuss with any of the package stuff manually then > you can even use the `pkg_manage' command to add and delete packages. > Jordan, You are right about this being somewhat suspect, but if you have limited disk space you might need to free some space. Deleting the contents of a ports directory seems (IMHO) better than say the manpages. 500MB fills up pretty quick (especially if you sup/ctm the source to help test behind the scenes:-). Yes, I know about pkg_*. I use it when necessary. I have found, however, that on ocassions pkg_delete does not delete all traces of an install package. Orphaned man pages seem to be the biggest problem. Also, `make install' registers the newly installed package with the pkg_*. Doesn't this create /var/db/pkg/.... which should contain ALL the info need by pkg_*.