Subject: Re: ${ENV} vs. ${SETENV}
To: NetBSD Packages Technical Discussion List <tech-pkg@NetBSD.org>
From: Jeremy C. Reed <reed@reedmedia.net>
List: tech-pkg
Date: 04/16/2005 07:02:38
Replying to two emails below:

On Sat, 16 Apr 2005, Alistair Crooks wrote:

> I know that Greg says that he's tried this and it's worked flawlessly,
> but that doesn't mean to say it will work for everyone.  What I'd like
> to hear from is people who have tried this on other environments.  If
> we could do this properly with minimal intrusion, it would be a good
> thing to have.

I started testing it yesterday on a couple different platforms. And I'll
keep on testing ...

On Sat, 16 Apr 2005, Roland Illig wrote:

> While we're at it, would you mind renaming SETENV to ENV_CMD? That is
> the pattern used for the other tools that have their "real name"
> environment variable reserved.

ENV_CMD sounds correct to me.

 Jeremy C. Reed

 	  	 	 open source, Unix, *BSD, Linux training
	  	 	 http://www.pugetsoundtechnology.com/