Date: Wed, 28 Jan 2004 00:26:53 +0100 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Kent Stewart <kstewart@owt.com> Subject: Re: Kopete 7.3 Message-ID: <4016F3BD.4040001@fillmore-labs.com> In-Reply-To: <20040127213718.GC68505@xor.obsecurity.org> References: <004401c3e4cf$647d91e0$c10133ce@dilkie.com> <200401271202.17222.kstewart@owt.com> <20040127213718.GC68505@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Tue, Jan 27, 2004 at 12:02:17PM -0800, Kent Stewart wrote: > >>>I always do a "make index" in the /usr/ports directory. Have I been >>>doing it wrong? >> >>No, I also use make index because historically there were significantly >>fewer error messages. I think someone almost got hysterical from >>surprise a short time ago when portsdb -U completed with out a single >>message. >> >>My attitude is that if Kris' script ran portsdb -U, then I would use it >>everytime I cvsup ports-all instead of using make index. > > AFAIK portsdb -U just calls 'make index' internally. The difference > would then presumably be caused by the make environment: my index > build tests simulate a clean environment by defining LOCALBASE, > X11BASE, etc. Not really. portsdb -U calls portsdb.update, which is defined in /usr/local/lib/ruby/site_ruby/1.6/portsdb.rb under 'def update' and calls /usr/local/sbin/make_describe_pass1 /usr/local/sbin/make_describe_pass2 /usr/ports/Tools/make_index But I guess knu is the expert here...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4016F3BD.4040001>