Date: Thu, 25 Jul 2013 00:58:12 +0300
From: Panagiotis Christias <p.christias@noc.ntua.gr>
To: freebsd-ports@freebsd.org
Subject: WITHOUT_NLS precedence over {UNIQUENAME}_SET or OPTIONS_FILE_SET?
Message-ID: <20130724215812.GA85865@noc.ntua.gr>
next in thread | raw e-mail | index | archive | help
Hello,
in my servers I add all global and per port build options in the
/etc/make.conf file, like this:
# Global options
WITHOUT_NLS=yes
[etc..]
# Per port options
.if $(.CURDIR:M*/mail/mailman)
mailman_SET+=MTA SENDMAIL NLS
.endif
.if $(.CURDIR:M*/sysutils/coreutils)
coreutils_SET+=NLS
.endif
[etc..]
In the above example, I was under the impression that
"mailman_SET+=NLS" or "coreutils_SET+=NLS" options would override
the global WITHOUT_NLS=yes definition but according to "make
showconfig" I was wrong.
Is this the correct behavior? To me at least it doesn't seem right.
To make things even more weird the following configuration works as
expected:
# Global options
WITHOUT_NLS=yes
# Per port options
.if $(.CURDIR:M*/mail/mailman)
mailman_SET+=MTA SENDMAIL
OPTIONS_FILE_SET+=NLS
.endif
.if $(.CURDIR:M*/sysutils/coreutils)
OPTIONS_FILE_SET+=NLS
.endif
That is, OPTIONS_FILE_SET+=NLS takes precedence over WITHOUT_NLS=yes
but {UNIQUENAME}_SET+=NLS doesn't.
Regards,
Panagiotis
--
Panagiotis J. Christias Network Management Center
P.Christias@noc.ntua.gr National Technical Univ. of Athens, GREECE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130724215812.GA85865>