Date: Fri, 14 Aug 2009 00:07:03 +0200 From: Polytropon <freebsd@edvax.de> To: PJ <af.gourmet@videotron.ca> Cc: freebsd-questions@freebsd.org Subject: Re: this is csup ? Message-ID: <20090814000703.bb91993d.freebsd@edvax.de> In-Reply-To: <4A8489ED.6040802@videotron.ca> References: <4A8489ED.6040802@videotron.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Aug 2009 17:47:25 -0400, PJ <af.gourmet@videotron.ca> wrote: > Please, please reassure me that I do come from Mars: > > What am I missing in the following? (direct quote from > http://www.shute.org.uk/misc/freebsd_uptodate.html : > > Then copy this script to /usr/local/sbin/ and run it when you want to > update your ports, source & docs. > #!/bin/sh > # > # Update source, docs and ports > > LOCAL_DIR="$(pwd)" > > cd /usr/src > make update > cd /usr/ports > make fetchindex Yes, the "make update" command either employs csup or cvsup (from ports, e. g. cvsup-without-gui). Which one is used is controlled by the setting in /etc/make.conf, for example: SUP_UPDATE= yes SUP= /usr/bin/csup SUPFLAGS= -g -L 2 SUPHOST= cvsup.freebsd.org SUPFILE= /etc/sup/stable.sup PORTSSUPFILE= /etc/sup/ports.sup Version control is done by the sup control files. If you do "make update" in /usr/src, I think the /usr/ports subtree will get updated, too. If not, don't forget to # cd /usr/ports # make update in order to update the ports. Note that there are other tools that can do that, too, e. g. portsnap. > echo "Now run:" > echo "# /usr/local/sbin/portsdb -u " > echo "# /usr/local/sbin/pkgdb -uvF " This is only important if you use tools like portupgrade. Erm, what was the initial question? -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090814000703.bb91993d.freebsd>