On Fri, Feb 9, 2018 at 12:04 PM, Alexey Dokuchaev <da...@freebsd.org> wrote:

> On Fri, Feb 09, 2018 at 11:50:35AM -0700, Warner Losh wrote:
> > On Fri, Feb 9, 2018 at 10:49 AM, John Baldwin <j...@freebsd.org> wrote:
> > > On Friday, February 09, 2018 03:50:33 PM Warner Losh wrote:
> > > > New Revision: 329064
> > > > URL: https://svnweb.freebsd.org/changeset/base/329064
> > > >
> > > > Log:
> > > >   We don't actually need env here, so drop it. All shells allow
> setting
> > > >   of shell variables for the next command like this.
> > >
> > > Eh:
> > >
> > > % LC_ALL=C env
> > > LC_ALL=C: Command not found.
> > >
> > > csh and tcsh don't let you set environment variables as a prefix.
> > >
> > > That said, if you try to use csh as the SHELL for make I bet many
> things
> > > would break.
> >
> > Right, all shells supported as SHELL for make. csh isn't on the list of
> > supported shells. Your bet is right: a lot of things do break.
>
> I don't really understand why we're discussing it: (t)csh, fish, whatever
> are for interactive use *only*.  Scripts (and makefiles) should only be
> written for standard plain POSIX shell.
>

Right. 'all shells' in my original simply meant that this has been a
feature of /bin/sh for long enough that we won't have anything to worry
about if we build on a foreign OS using something weird like bash.

Warner
_______________________________________________
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Reply via email to