Date: Sat, 10 Jul 2010 18:53:45 +0200 From: Polytropon <freebsd@edvax.de> To: bf1783@gmail.com Cc: Aiza <aiza21@comclark.com>, Polytropon <freebsd@edvax.de>, "b. f." <bf1783@googlemail.com>, freebsd-questions@freebsd.org Subject: Re: how to setenv using Bourne .sh Message-ID: <20100710185345.4d3b69bf.freebsd@edvax.de> In-Reply-To: <AANLkTiklf4jVVPXKsSKAYHHas9t4mhfBgm-BMBokTb5F@mail.gmail.com> References: <AANLkTiklf4jVVPXKsSKAYHHas9t4mhfBgm-BMBokTb5F@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Jul 2010 11:43:13 +0000, "b. f." <bf1783@googlemail.com> wrote: > Polytropon wrote: > On Sat, 10 Jul 2010 10:53:17 +0800, Aiza <aiza21 at comclark.com> wrote: > >> Trying the set the pkg_add environment variable PKGDIR using this > >> > >> > >> setenv PKGDIR="/usr/packages" and get this error message > >> setenv: Syntax Error. > > > >Of course. The sh shell doesn't have setenv. > > It looks like he is actually using csh, because in the Bourne shell > issuing that command usually yields "setenv: not found". His problem > is that, unlike "export", setenv doesn't take an "=" between the > variable and the value to be assigned to it. See csh(1). Yes, you're right of course, I didn't notice that. The correct syntax for the setenv command in the C shell is setenv VAR "value" > When you are directed to builtin(1), it usually means that you should > refer to the manpage(s) of the shell that you are using for the > information that you need. That's why I suggested looking at csh's manpage. :-( -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100710185345.4d3b69bf.freebsd>