Date: Thu, 01 Mar 2012 11:24:38 +0000
From: Matthew Seaman <matthew@FreeBSD.org>
To: freebsd-ports <freebsd-ports@FreeBSD.org>
Subject: On the usage of ${FILE}
Message-ID: <4F4F5C76.8040908@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig51D4FC00AFF1A246E1C0EECD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Dear all,
bsd.commands.mk has the following:
FILE?=3D /usr/bin/file
which is unfortunate, given that ${FILE} is used in several thousand
ports, generally as a loop control variable for iterating through a list
of files. In fact, I can only find about 8 places where the file(1)
program is intended.
This obvious conflict of meanings seems pretty undesirable to me. Am I
missing something? Is there any reason to keep the status quo rather
than changing the bsd.commands.mk variable to FILE_CMD and making the
corresponding changes in those 8 places?
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
--------------enig51D4FC00AFF1A246E1C0EECD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9PXHwACgkQ8Mjk52CukIzuLQCfSg0ZzYQZqxAn+GsYJBfttOCJ
wSQAn0mUTf162THJDD5jbl7QhQQ/y701
=crJM
-----END PGP SIGNATURE-----
--------------enig51D4FC00AFF1A246E1C0EECD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F4F5C76.8040908>