Martti Kuparinen wrote:
> I just ran "pkglint -Wall" on some of my packages and I noticed these:
> 
> 
> NOTE: Makefile:121: You can write "cp" instead of "${CP}".
> NOTE: Makefile:124--126: You can write "env" instead of "${SETENV}".
> NOTE: Makefile:137: You can write "rm" instead of "${RM}".
> NOTE: Makefile:144--145: You can write "sh" instead of "${SH}".
> 
> 
> Since when (and why?) is the use of "cp" preferred over "${CP}"?
> 
> Martti

AFAIK it's not only cp.  A few others including mv, find, xargs, chown
etc. also generate this note.

$ pkglint -Wall -e
NOTE: Makefile:63: You can write "cp" instead of "${CP}".

        The wrapper framework from pkgsrc takes care that a sufficiently
        capable implementation of that tool will be selected.

adrian.