ports/165623: Mk/bsd.comands.mk et al -- conflicting uses of ${FILE}

Matthew Seaman m.seaman at infracaninophile.co.uk
Fri Mar 2 23:37:21 UTC 2012


On 02/03/2012 21:20, Michael Scheidell wrote:
>  does portlint need to be upgraded to tell you to use ${FILE_CMD} instead 
>  of ${FILE} ?

Perhaps, but that's going to annoy the vast majority of people that use
${FILE} to mean something other than the file(1) application.  I tend
towards the view that there's so much prior art, and that saying:

.for FILE in ${LIST_OF_FILES}
...
.endfor

is so natural a construct that trying to make people do it differently
would be wildly unpopular.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
JID: matthew at infracaninophile.co.uk               Kent, CT11 9PW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/attachments/20120302/ac0fbaeb/attachment.sig>


More information about the freebsd-ports-bugs mailing list