Roland Illig wrote:
> 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 ENV and provide a fallback 
> SETENV?=${ENV} for the time of transition.

Replaced all SET with ENV (was a typo).

Roland