Subject: Curious deprecated option handling
To: None <email@example.com>
From: Jeroen Ruigrok/asmodai <firstname.lastname@example.org>
Date: 09/02/2005 15:35:57
I got interested in how the deprecated options got handled when it seemingly
seems not to reflect a pkg reality.
Take for example audio/esound.
When one does the following:
$ bmake show-options
Any of the following general options may be selected:
inet6 Enable support for IPv6.
These options are enabled by default:
These options are currently enabled: inet6
Deprecated variable USE_INET6 used, use PKG_DEFAULT_OPTIONS+=inet6 instead.
$ grep -R USE_INET6 *
It is also not one of its dependencies. Where I am placing my money on is
# if the system is IPv6-ready, compile with IPv6 support turned on.
. if empty(USE_INET6:M[Yy][Ee][Ss]) || defined(USE_SOCKS)
.elif empty(_OPSYS_HAS_INET6:M[nN][oO]) && !defined(USE_SOCKS)
And indeed, when I comment this the warning disappears. There is some logic
to be rethought here.
What's the case about USE_INET6 for non-options.mk using pkgs? Is that
allowed or is that also logic that needs to be reordered?
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://www.andf.info/
http://www.tendra.org/ | http://www.in-nomine.org/
I have not yet begun to fight...