On Wed, Aug 23, 2006 at 01:51:52PM -0700, Doug Barton wrote: > 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. > True. The implementation is also smart -- it doesn't spam make(1) environment when not necessary. Thanks!
Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer
pgp0L5O42e3js.pgp
Description: PGP signature