On Wed, Mar 08, 2000 at 12:17:26PM +0100, Brad Knowles wrote:
> At 12:45 PM +0200 2000/3/8, Panagiotis Astithas wrote:
> It doesn't seem to be quite working. Cd'ing to /usr/src and then
> typing "make update" doesn't seem to be grabbing the crypto stuff
> (which goes to a different server),
You should see three cvsup sessions:
a) Using SUPFILE (all sources except crypto)
b) Using SUPFILE1 (crypto stuff)
c) Using PORTSSUPFILE (the ports)
These variables are set in /etc/rc.conf. It's your job to make sure that
they're pointing to the correct files and that the files are valid cvsup
configuration files for the intended purpose.
I'm using this setup for a long time and it works.
> and I wouldn't want it to grab the /usr/ports stuff without my explicitly
> going in to /usr/ports and also typing "make update".
That's one of the things I don't like. And I can't understand why a "make
update" should include the ports but not /usr/doc. Which is another reason
why I don't like this behaviour.
I've hacked my Makefiles to include the update for the /usr/doc -- and to
check NOPORTUPDATE and NODOCUPDATE. Their effects should be obvious.
Patch (relative to -current) available on request, I'll file a PR after
4.0-RELEASE.
/s/Udo
--
I have learned over the years, that if it is the truth you seek, then
honesty on your own part, is the best policy. That and torture.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
