Date: Sun, 25 Sep 2005 13:07:29 +0100 From: Chris <chris@childeric.freeserve.co.uk> To: freebsd-questions@freebsd.org Subject: Re: portupgrade + make_ports.sh: Fixing everything in one go Message-ID: <43369301.3020501@childeric.freeserve.co.uk> In-Reply-To: <43358463.6030803@ywave.com> References: <20050924141218.CE8F416415C@ws1-4.us4.outblaze.com> <43358463.6030803@ywave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Micah wrote: > > > Fafa Hafiz Krantz wrote: > >> Hello! >> >> I thought I'd ask you all if my make_ports.sh is as convenient as I think >> it is, or if it's totally off track or what not: >> >> # cat make_ports.sh >> >> cvsup -g -L 2 /etc/cvsupfile >> cd /usr/ports >> make fetchindex >> portupgrade -raP >> portsdb -uU Not the answer to your main question but you only need portsdb -u after you use make fetchindex. -U rebuilds the index which takes a _long_ time on a slow computer and is not necessary if you've just fetched it. Also I'm not clear if one needs the ports tree and INDEX up to date to upgrade using packages, but the portsdb command should be before the portupgrade command (and after make fetchindex). A good read of man pages and the handbook helped me. >> pkgdb -F >> portsclean -CDLP > Which version of FreeBSD are you running? Seems that pre-compiled > packages are only available for the latest release (5.4 right now). You can get packages which are about as current as the ports by setting PACKAGESITE. Eg in csh setenv PACKAGESITE ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/packages/Latest/ then pkg_add -r whatever works pretty well for me (it needs the trailing forward slash). I've just discovered this so am pretty happy :) Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43369301.3020501>
