On Tuesday 22 June 2004 11:34, you wrote:
> > 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.
> If you are to run it after you cvsup ports-all, what do you think it is
The INDEX file that get cvsup'ed when I cvsup ports? I only sup ports once a
month or so unless I'm installing something new, so I guess I'm getting a new
INDEX most times.
> In addition, portsdb -U now runs "make index" but you would have to
> search -ports@ to read about that change. You can read comments about
> it on
> see the commit message for version 1.78.
Well, I don't track -ports, so, yes I missed that.
I'm not trying to be combative here, I was wrong, a bit. I gave the portsdb
man page a quick once-over a while ago (when I started using portupgrade)
and thought I understood what it was doing. I didn't realize the -U was
regen'ing INDEX from the current ports tree, as I didn't realize that INDEX
was updated with less frequency that the tree, so I didn't realize that was
even needed, though it's obvious once I think about it.
It also explains why portsdb -Uu takes so freekin' long sometimes, which had
been bugging me.
> > 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
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"