Re: cvsupit assumptions (was: Re: Re[2]: Can't build current...)

[Kris Kennaway]

On Wed, Mar 28, 2001 at 09:15:51PM +0200, Gabriel Ambuehl wrote:

> Oh and while I'm on it: where is src/crypto/rijndael in the CVS?

in src/sys/crypto/rijndael :-)

> CVSWEB doesn't find it, neither does it get downloaded (this time
> using a complete supfile ;-)...

You need the src-sys-crypto cvsup collection.

Kris

 PGP signature

Re: cvsupit assumptions (was: Re: Re[2]: Can't build current...)

[Gabriel Ambuehl]

-BEGIN PGP SIGNED MESSAGE-

Hello Robert,

Tuesday, March 27, 2001, 8:19:42 PM, you wrote:

> 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.

Actually, it doesn't even ask the user what to do with crypto if 5
CURRENT is selected (can't remember for sure what it did when one
selected 4 STABLE). So even if the user selects everything that is
presented to him, src-crypto and src-secure won't be in the cvsup file
and thus a normal attempt to build the system will break. Guess it is
time to formulate a PR on this...

Oh and while I'm on it: where is src/crypto/rijndael in the CVS?
CVSWEB doesn't find it, neither does it get downloaded (this time
using a complete supfile ;-)...

(although I managed to get the necessary files after searching with
google but obviously they are not on the FreeBSD site. Those seem to
be used only by the kernel as world will build without them.)


Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

iQEVAwUBOsIqW8Za2WpymlDxAQF9pwgAtVjLwwE561veqFCtW7MsZ/j/qBj5NDAx
UTaqNneKx4HRBrt5xfVS0LLwYyr3HubUzvnJy7rIa24h+/7YXwQQGzVphitF3meo
VaQYIB+hei6ZSCuywXpoVnYEikkMBuHRaM/BxtajTWBTeugsPQX+83L6/yVQfHSr
FF1ttkTcyCnLHQLTrz+zevtmBlRaZNyBJAMgKkDGAVqQQSFIF7mniJStlEnZsq9B
J1tBWHrBQjLG2Y7CkGn3WaDO5VBrCMn9fvQTQoBZUmTJ7+AGjkyWILyeMZ/iPL87
j7rcRpLyqgGlNva83pr2p3qQxeE662nbW9z/IdENdCqc4hyU8pzGzA==
=cAKe
-END PGP SIGNATURE-



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

cvsupit assumptions (was: Re: Re[2]: Can't build current...)

[Robert Watson]

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
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message