cvsup and ports INDEX

[Matt Navarre]

On Tuesday 22 June 2004 09:51, Kent Stewart wrote:
> 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,
<snip>
> >
> > 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

That's not what the man page implys:


    "The portsdb command is a tool to generates the ports database named
     INDEX.db from the ports index file named INDEX.  It is commonly used
     among the tool suite and automatically updated on demand when it gets
     older than the index file"

I'm not sayin' you're wrong, since I read that a long while ago and haven't 
needed to know anything more about portsdb since, but you and the description 
in portsdb(1) seem to disagree.

Yes, the -U option does "Update or create the ports index file called INDEX", 
it's just not evident from the description that it can use the installed 
ports tree.

So I was kinda right. A little :)


> Kent

Matt
-- 
"We all enter this world in the same way: naked, screaming,
 and soaked in blood. But if you live your life right, that kind
 of thing doesn't have to stop there." -- Dana Gould