Date: Tue, 20 Apr 2004 21:26:41 -0400 From: Jim Trigg <jtrigg@spamcop.net> To: freebsd-ports@freebsd.org Subject: Re: Lost portupgrade functionality building INDEX Message-ID: <20040421012641.GA36748@spamcop.net> In-Reply-To: <20040420222517.GA68354@xor.obsecurity.org> References: <20040420210902.GA35257@spamcop.net> <20040420222517.GA68354@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 20, 2004 at 03:25:17PM -0700, Kris Kennaway wrote:
> On Tue, Apr 20, 2004 at 05:09:02PM -0400, Jim Trigg wrote:
> > While I understand the reasoning behind making portsdb -U use "make
> > index" behind the scenes, it kills a bit of functionality. portsdb -U
> > no longer honors pkgtools.conf, so options set there will not be
> > reflected in the dependencies shown in INDEX. If I knew ruby, I'd try
> > to write a new portsdb -U function, but I don't. Is there any way we
> > can get this functionality back while maintaining compatibility with
> > make index in other ways?
>
> Set your config options in make.conf instead of pkgtools.conf.
That's what I'm doing for the time being, but it loses the port-by-port
granularity. I can't, for instance, build one port with MySQL support,
another with PostgreSQL support, and another which could support either
with neither.
Jim
--
Jim Trigg, Lord High Everything Else O- /"\
\ / ASCII RIBBON CAMPAIGN
Hostmaster, Huie Kin family website X HELP CURE HTML MAIL
Verger, All Saints Church - Sharon Chapel / \
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040421012641.GA36748>