Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Oct 2011 10:24:42 +0000 (GMT)
From:      "Thomas Mueller" <mueller6727@bellsouth.net>
To:        freebsd-questions@FreeBSD.org
Subject:   Re: csup: How do I know I have correct version?
Message-ID:  <20111023102445.3102C106566B@hub.freebsd.org>
References:  <4EA1411B.3050300@infracaninophile.co.uk> <4EA13FA9.9030405@my.gd> <201110221023.p9MAN4NW007056@smtp.infracaninophile.co.uk> <4EA29FA1.2040706@infracaninophile.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
from Matthew Seaman <m.seaman@infracaninophile.co.uk>:

> Don't define PORTSSUPFILE in /etc/make.conf if you're using portsnap(1).
>  Apart from anything else, typing 'make update' in /usr/src will attempt
> to cvsup not just the system sources but as well any of PORTS, DOC where
> you've defined a ...SUPFILE.
 
> In fact, without PORTSUPFILE defined in /etc/make.conf typing 'make
> update' in /usr/ports will invoke portsnap for you, so long as you
> obtained the ports tree by 'portsnap fetch extract' originally.
 
>         Cheers,
 
>         Matthew

Now I know better how 'make update' works, though I looked at that target in /usr/src/Makefile.

I find from experience that updating ports by two different means makes a mess or at least doesn't work.

In 9.0-BETA1, I tried 'portsnap fetch update' some time after having installed the ports tree from the bsdinstall.

That didn't work, and I had to 'portsnap fetch' and 'portsnap extract' as if I had never installed the ports tree from the bsdinstall.

I guess then I can install the docs by 'csup /usr/share/examples/doc-supfile' ?  

That would be simpler and easier than installing misc/freebsd-doc-en from the ports.

Tom




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111023102445.3102C106566B>