Subject: ${SET} vs. ${SETENV}
To: None <>
From: Roland Illig <>
List: tech-pkg
Date: 04/08/2005 19:03:37
Hi all,

I wonder why the variable for the command set(1) is called SETENV 
instead of ENV (see mk/platform/*.mk for definitions). Is there any 
special reason for it to differ from the convention that each tool gets 
its uppercase name as a variable?

If not, I'd like to rename SETENV to SET and provide a fallback 
SETENV?=${SET} for the time of transition.