Date: Sat, 25 Oct 2003 15:42:00 -0400 From: Richard Coleman <richardcoleman@mindspring.com> To: FreeBSD ports <ports@FreeBSD.org> Subject: Re: ports/58525: [PATCH] port devel/portlint: USE_* should be no user-settable option Message-ID: <3F9AD208.7050901@mindspring.com> In-Reply-To: <20031025190643.10331.qmail@laurel.tmseck.homedns.org> References: <20031025190643.10331.qmail@laurel.tmseck.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> While I appreciate your effort to clean up the USE_* namespace, this
> seems somewhat half-baked to me. Why not go one step further: no port
> should be allowed to use the USE_<OPTION> namespace for user specified
> options. Instead, they should use the USE_<PORT>_OPTION or
> WITH{,OUT}<PORT>_OPTION (or <PORT>_{USE,WITH,WITHOUT}_, for what it's
> worth) namespace. Variables in the USE_<OPTION> namespace should only be
> specified by portmgr@ for internal use or to set "global" dependencies,
> similar to Gentoo Linux's "use=".
>
> Implementing this would enable one to specify all tunables one wants to
> set in a central location like /etc/make.conf without having to fear
> bizarre side effects and without having to resort to a bunch of
> Makefile.locals or portupgrade and its MAKE_ARGS facility.
Even if you add code to prohibit using the USE_* namespace (which is a
good idea), it still makes sense to add this patch to portlint to warn
about such namespace pollution. Patching portlint is probably the best
way to get moving towards exactly what you want.
Richard Coleman
richardcoleman@mindspring.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F9AD208.7050901>