Date: Thu, 25 Jul 2002 20:09:40 +0300 From: Ruslan Ermilov <ru@FreeBSD.ORG> To: Cyrille Lefevre <cyrille.lefevre@laposte.net> Cc: Bruce Evans <bde@zeta.org.au>, Doug Barton <DougB@FreeBSD.ORG>, Mike Barcroft <mike@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: Standardized make options (or no doesn't always mean no) Message-ID: <20020725170940.GA40574@sunbay.com> In-Reply-To: <20020725165940.GF58642@gits.dyndns.org> References: <3D02AB11.F373AB4@FreeBSD.org> <20020609123557.X21758-100000@gamplex.bde.org> <20020725070145.GE56367@sunbay.com> <20020725165940.GF58642@gits.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jul 25, 2002 at 06:59:40PM +0200, Cyrille Lefevre wrote:
> On Thu, Jul 25, 2002 at 10:01:45AM +0300, Ruslan Ermilov wrote:
> > On Sun, Jun 09, 2002 at 12:42:59PM +1000, Bruce Evans wrote:
> > > On Sat, 8 Jun 2002, Doug Barton wrote:
> > > > Mike Barcroft wrote:
> > > > > Is anyone planning to do something about the hugely confusing sta=
te of
> > > > > NO/NO_ options? I can never remember which options have an under=
score
> > > > > after the NO, so I end up writing commands like
> > > > > `make kernel ... NO_KERNELCLEAN=3Dtrue NOKERNELCLEAN=3Dtrue'. It=
would
> > > > > very nice if we could standardize this and add some compatibility
> > > > > shims for historical spellings.
> > > >
> > > > In the past versions of this conversation, the general agreement is=
that
> > > > going forward we should probably standardize on underscores to sepe=
rate
> > > > words. So, NO_FOO rather than NOFOO. However, no_volunteer has come
> > > > forward to do the work you've described, so if you're volunteering.=
...
> > > > :)
> > >=20
> > > On my list of things to fix after the changing the spelling of "nothi=
ng"
> > > to "no thing". :-) :-)
> > >=20
> > I'd volunteer to do it if we could come up to a (violent) agreement.
> >=20
> > We'd provide the compatibility knobs that would also trigger a warning
> > (a .warning to be added to make(1)) that NO_FOO should now be used
> > instead of NOFOO (or vice versa, if we decide to go that way).
>=20
> .warning isn't needed, let's try w/ .BEGIN :)
>=20
> NOBAD=3D true
> NO_GOOD=3Dtrue
> NOWARN=3D true
> NO_WARN=3Dtrue
> NOERR=3D true
> NO_ERR=3D false
>=20
> _NO_VARS=3D BAD GOOD WARN ERR TOTO
>=20
> .BEGIN:
> .for var in ${_NO_VARS}
> .if defined(NO${var})
> . if defined(NO_${var})
> . if ${NO${var}} !=3D ${NO_${var}}
> # maybe this should be a .error ?
> @${ECHO_CMD} "warning: both NO_${var} and NO${var} are defined and" \
> "have different values -- using NO_${var} and unsetting NO${var}."
> . else
> @${ECHO_CMD} "warning: both NO_${var} and NO${var} are defined" \
> "-- using NO_${var} and unsetting NO${var}."
> . endif
> . else
> @${ECHO_CMD} "warning: NO_${var} should be defined in place of NO${var}"=
\
> "-- setting NO_${var} as NO${var} and unsetting NO${var}."
> . endif
> .endif
> .endfor
>=20
> .for var in ${_NO_VARS}
> .if defined(NO${var})
> . if !defined(NO_${var})
> NO_${var}:=3D${NO${var}}
> . endif
> . undef NO${var}
> .endif
> .endfor
>=20
> all:
> @${ECHO_CMD} BAD=3D${NOBAD}:${NO_BAD}
> @${ECHO_CMD} GOOD=3D${NOGOOD}:${NO_GOOD}
> @${ECHO_CMD} WARN=3D${NOWARN}:${NO_WARN}
> @${ECHO_CMD} ERR=3D${NOERR}:${NO_ERR}
>=20
> a non-exhaustive list of NO[^_] variable is :
>=20
> NOTAGS NODOCCOMPRESS NOINFO NOINFOCOMPRESS NOPIC NOPROFILE NOEXTRADEPEND
> NOFCSCHG NOSHARED NOMAN NOMANCOMPRESS NOMLINKS NOOBJ NOSGMLCOMPRESS
> NOCLEAN NOCLEANDIR NOMAN NOGAMES NOPERL NOLIBC_R NOHTML NODOC
> NOKERBEROS NOPORTREADMES NOPORTS NOSRC NODESCRYPTLINKS NOCRYPT
> NOSECURE NOSHARE NOFORTH NOLIB NOPAM NOUUCP NOALIAS NOI4B NOINET6
> NOKLDLOAD NONAT NONETGRAPH NORADIUS NOSUID NOIPSEC
>=20
> I'll try to make another knob for variable conversion such as :
> NOALIAS -> PPP_NO_ALIAS, etc.
>=20
> > I would personally prefer the NO_FOOs since these would make things
> > more readable and disambiguate the things like NORMAL, NOTES, NODES.
> > What's NODES? node(s) or "no DES"? :-)
>=20
> agreed.
>=20
Sounds like a plan. :-)
Cheers,
--=20
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE9QDDUUkv4P6juNwoRAomcAJ9gL9HhlJCxUPlKr5PKj2RAb00eKACeJGNs
1ycTCzsZlgLLnMA5nEA4zeo=
=U3Br
-----END PGP SIGNATURE-----
--M9NhX3UHpAaciwkO--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020725170940.GA40574>