Date: Wed, 23 Aug 2006 13:51:52 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Ruslan Ermilov <ru@freebsd.org> Cc: Vivek Khera <vivek@khera.org>, "Todorov @ Paladin" <todorov@paladin.bulgarpress.com>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: 5.5 to 6.1 upgrade Message-ID: <44ECBFE8.7000809@FreeBSD.org> In-Reply-To: <20060823193309.GA77890@rambler-co.ru> References: <Pine.BSF.3.96.1060823010930.9072A-100000@gaia.nimnet.asn.au> <5B7BD83A-6316-4C20-903E-B5D66D4F2642@khera.org> <44EB5354.6070007@paladin.bulgarpress.com> <F55D8A99-A30E-49DB-94F3-8A1737CF7556@khera.org> <44EB6411.4040406@paladin.bulgarpress.com> <20060823193309.GA77890@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote:
> On Tue, Aug 22, 2006 at 11:07:45PM +0300, Todorov @ Paladin wrote:
>> Also - why portupgrade is not always aware of
>> previously chosen options for a port build?
>>
> It depends. If options are OPTIONS (in the ports sense), they
> are saved and independent of portupgrade. If options are
> makefile options specified in pkgtools.conf, they are only
> taken into accont if the port is (re)build explicitly; they
> are not taken into account if a port is (re)built as a
> dependency of another port. In plain text: if port B has
> options in pkgtools.conf, and port A has B as its dependency,
> and you portinstall/portupgrade A, B will be built (if needs
> be) without pkgtools.conf options. Be careful.
sysutils/portconf does not have that limitation. If you specify flags using
that method, they will always be used.
FYI,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44ECBFE8.7000809>