Date: Sat, 26 Aug 2006 22:42:10 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: 5.5 to 6.1 upgrade Message-ID: <44F130B2.8010702@FreeBSD.org> In-Reply-To: <20060827002203.A39026@atlantis.atlantis.dp.ua> 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> <44ECBFE8.7000809@FreeBSD.org> <20060824082012.GA81296@rambler-co.ru> <20060827002203.A39026@atlantis.atlantis.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Dmitry Pryanishnikov wrote:
> I've tried to use sysutils/portconf, but found that it still doesn't
> give an universal solution:
I think we need to be careful what our expectations of "universal" are with
a ports tree as large, and a userbase as diverse, as what we have. However ...
> 1) it doesn't work if /usr/ports is a link to another location.
Sure it does. You just have to be smarter about how you specify the triggers
in make.conf. :) I have the following:
.if !empty(.CURDIR:M/mnt/slave/space/ports*)
# Begin portconf settings
...
Works like a charm.
> 2) it still doesn't affect OPTIONS (in the ports sense); try e.g. the
> following:
If it's not working at all to start with (as you specified above), then this
additional example of brokenness is meaningless. Additionally, OPTIONS
ignores settings in the environment at all times to start with. It's easy
enough to test this for yourself by placing something in make.conf.
hth,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44F130B2.8010702>