Date: Wed, 05 Sep 2007 19:34:56 +0100 From: Adam J Richardson <fatman@crackmonkey.us> To: "Michael C. Cambria" <mcc@fid4.com> Cc: questions@freebsd.org Subject: Re: /usr/ports & portupgrade when only using packages Message-ID: <46DEF6D0.8010108@crackmonkey.us> In-Reply-To: <46DECE7F.3000909@fid4.com> References: <46DECE7F.3000909@fid4.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael C. Cambria wrote: > I need to set up a system that can only use packages. I've always used > ports, so I'm not exactly sure if I'm doing things properly. > > Should I (do I need to) use portsnap to populate /usr/ports? Unless I > really need something that doesn't have a pkg available, I will not be > using ports. > > I've always used portupgrade, and plan to do so, using -PP (only > packages) for this setup. My first question is should I? > > Doing'pkg_add -r portupgrade' and it installed fine. > Using pkgdb -F however, resulted in these messages: > > bsd# pkgdb -F > cd: can't cd to /usr/ports > cd: can't cd to /usr/ports/ports-mgmt/portupgrade > cd: can't cd to /usr/ports > ----> Chcecking the package registry database > > Any help appreciated. Hi Mike. Let me see if I've got this... you want to be able to install packages, but not ports. Well, that's easy... # rm -R /usr/ports Saves you a load of disk space, too. The only downside is you get slightly older versions of software with packages. Oh, and don't use portsnap, it'll undo that "rm -R" for you. Using "portupgrade -PP" works perfectly well on those rare occasions when I want to install a package rather than a port. I guess you could delete all executables matching "port*", but that might be going too far. You could get rid of two of those error messages by doing a: # mkdir /usr/ports Regards, Adam J Richardson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46DEF6D0.8010108>