cvsup and ports INDEX

[Kent Stewart]

On Tuesday 22 June 2004 09:27 pm, Matt Navarre wrote:
> On Tuesday 22 June 2004 07:05, epilogue at allstream.net wrote:
> > hello all,
> >
> > Connecting to cvsup.ca.FreeBSD.org
> > Connected to cvsup.ca.FreeBSD.org
> > Server software version: SNAP_16_1e
> > Negotiating file attribute support
> > Exchanging collection information
> > Establishing multiplexed-mode data connection
> > Running
> > Updating collection ports-all/cvs
> >  Checkout ports/INDEX             <<<<<<< how is this different
> > from...
>
> This checks out the new ports text file.
>
> > # portsdb -Uu                          <<<<<<< ...this?
>
> This builds INDEX.db, which is all the ports/dependency information
> in the format that portupgrade(and others?) uses so it can get all
> the right ports when you install something.
>
> > i'm not sure i have a firm grasp of why i do both.  are they
> > complimentary or redundant steps?  could someone please clarify or
> > point me to right set of docs?
>
> They're complimentary, portsdb -uU doesn't really do anything unless
> you have a new /usr/ports/INDEX or /usr/ports/INDEX.db got hosed.

This isn't true. Portsdb -U creates a brand new INDEX using your 
current /usr/ports and -u uses that to generate a new INDEX.db

Kent

>
> > hello ken,
> >
> > thought that you might be able to help because of your reply on
> > http://lists.freebsd.org/pipermail/freebsd-ports/2004-June/013223.h
> >tml
> >
> >
> > thanks,
> > epi
> > _______________________________________________
> > 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"

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html