Date: Sun, 27 Aug 2006 00:42:24 +0300 (EEST) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: Ruslan Ermilov <ru@freebsd.org> Cc: Doug Barton <dougb@freebsd.org>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: 5.5 to 6.1 upgrade Message-ID: <20060827002203.A39026@atlantis.atlantis.dp.ua> In-Reply-To: <20060824082012.GA81296@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> <44ECBFE8.7000809@FreeBSD.org> <20060824082012.GA81296@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello!
On Thu, 24 Aug 2006, Ruslan Ermilov wrote:
>>> It depends. If options are OPTIONS (in the ports sense), they
>>> are saved and independent of portupgrade. If options are
>> 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!
I've tried to use sysutils/portconf, but found that it still doesn't
give an universal solution:
1) it doesn't work if /usr/ports is a link to another location. Try e.g.
the following configuration:
root@homelynx# ls -l /usr/ports
lrwxr-xr-x 1 root wheel 9 Aug 27 00:27 /usr/ports -> ftp/ports
root@homelynx# cd /usr/ports/net/quagga
root@homelynx# realpath .
/usr/ftp/ports/net/quagga
root@homelynx# grep quagga /usr/local/etc/ports.conf
net/quagga: WITH_SNMP=yes
root@homelynx# make -V WITH_SNMP
root@homelynx#
Ports infrastructure itself works OK in this configuration, but
sysutils/portconf does not.
2) it still doesn't affect OPTIONS (in the ports sense); try e.g. the
following:
root@homelynx# realpath .
/usr/ports/net/quagga
root@homelynx# rm -rf /var/db/ports/quagga
root@homelynx# grep quagga /usr/local/etc/ports.conf
net/quagga: WITH_SNMP=yes
root@homelynx# make
You'll see the options menu, and "SNMP support" will be unchecked, so
WITH_SNMP will be ignored by the port.
Sincerely, Dmitry
--
Atlantis ISP, System Administrator
e-mail: dmitry@atlantis.dp.ua
nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060827002203.A39026>