Date: Thu, 01 Mar 2007 09:58:06 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Ed Schouten <ed@fxq.nl> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Milan Obuch <freebsd-current@dino.sk> Subject: Re: /etc/make.conf oddity (?) Message-ID: <45E7142E.6020900@FreeBSD.org> In-Reply-To: <20070301080449.GO11232@hoeg.nl> References: <200703010829.18334.freebsd-current@dino.sk> <20070301080449.GO11232@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ed Schouten wrote:
> I once had this issue as well. Keep in mind that /etc/make.conf is a
> Makefile, not a shellscript. In Makefiles you don't need to quote your
> variables. In shell scripts you do, because the second argument will be
> treated as a command.
Just to be a little pedantic, you need to quote variables _if_ there
is more than one of them.
foo="bar"
and
foo=bar
are functionally equivalent, whereas
foo="bar baz"
and
foo=bar baz
mean two very different things, as you suggest above.
If you want to see good examples of when quoting might be needed for
make, check out ports-mgmt/portconf.
hth,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45E7142E.6020900>