From owner-freebsd-current Tue Mar 27 10:19:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 175E637B718 for ; Tue, 27 Mar 2001 10:19:54 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2RIJhh94062; Tue, 27 Mar 2001 13:19:43 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 27 Mar 2001 13:19:42 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Gabriel Ambuehl Cc: Makoto MATSUSHITA , freebsd-current@freebsd.org Subject: cvsupit assumptions (was: Re: Re[2]: Can't build current...) In-Reply-To: <74288556332.20010327201141@buz.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Mar 2001, Gabriel Ambuehl wrote: > I'm using cvsup.de.FreeBSD.org which appears to be a cname > cvsup.uk.FreeBSD.org. But it looks like, that for some reason, > src-secure didn't get added to the cvsupfile (hmm. might be related to > the fact that cvsupit creates cvsup.intl for that purpose and I forgot > to add that one to make.conf...). Mea culpa (hope it will work now). I've actually heard that from a couple of other people lately -- that cvsupit still assumes that crypto should not be pulled down, and the crypto code is now assumed in the default build. This may just be a product of the packagized version of cvsupit shipped in the past, but it might also be the case that cvsupit needs to be updated to take into account changes in our cvsup policies and source layout. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message