Ports Collection and FreeBSD 5.2.1

[Arend P. van der Veen]

I think I figured out the problem that I was having.  I compiled 
portupgrade before I performed a cvsup and rebuilt the kernel.  Now I 
run cvsup, rebuild the kernel, install portupgrade (and pkgtools 
dependency) using make install and then execute portsdb -Uu.

When I perform these steps the problems that I had cleared up.  It was a 
stupid mistake on my part. 

I do have an additional question.  I thought that my cvsup input was 
setup to load the complete ports collection.  Specifically, the line

ports-all tag=.

loads the complete ports collection.  Is this correct ?

Thanks for your help,
Arend

Lowell Gilbert wrote:

>"Arend P. van der Veen" <apv at capital.net> writes:
>
>  
>
>>I have been recently testing FreeBSD 5.2.1.  I load the initial system
>>from CD, install and configure cvsup and then download all of the src
>>and port changes.  My supfile is:
>>
>>*default host=cvsup2.us.FreeBSD.org
>>*default base=/usr
>>*default prefix=/usr
>>*default release=cvs tag=RELENG_5_2
>>*default delete use-rel-suffix compress
>>
>>src-all
>>ports-all tag=.
>>
>>I then execute:
>>
>>cvsup -g -L 2 /usr/sup/supfile
>>portsdb -Uu
>>
>>portsdb returns a lot of warnings about dependency lists.  I do not
>>have this problem under 4.10.
>>
>>Does anybosy have any idea what I am doing wrong or is there something
>>different in the ports collection under 5.X.
>>    
>>
>
>You don't have the full ports collection.
>These warnings have been broken lately, but I believe the plan is to
>fix them and make them fatal (so everyone will have to get the full
>ports collection if they want to build their own INDEX).
>_______________________________________________
>freebsd-questions at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>
>  
>