Date: Mon, 20 Jun 2005 17:09:41 -0500 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Garance A Drosehn <gad@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Tim Robbins <tjr@FreeBSD.org> Subject: Re: cvs commit: src/usr.bin/env env.c Message-ID: <20050620220941.GB78993@over-yonder.net> In-Reply-To: <p06210226bedca69d3945@[128.113.24.47]> References: <200506200314.j5K3EUtt089472@repoman.freebsd.org> <20050620094103.GB54301@cat.robbins.dropbear.id.au> <p06210226bedca69d3945@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 20, 2005 at 01:47:59PM -0400 I heard the voice of Garance A Drosehn, and lo! it spake thus: > > >Also, please be careful when adding new non-standard options and > >features; they tend to stick around forever. > > These *are* intended to stick around forever. In fact, they are > designed in such a way that other OS's could pick up the changes. Well, FWIW, it DID occur to me (I just ignored it, because it seemed kinda irrelevant and nit-picky) that it might be more approprate to have an external utility (`runinterp` or something) to do that splitting, rather than grafting it onto env. I think of env as a way to set environmental variables, not as a way to execute programs. It might be easier to convince other OS's "Here, have a package for this utility" than "Here, change your env to work like this", too. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050620220941.GB78993>