SVN commit 1190780 by rkcosta:
Backport r1190779.
Properly quote the call to 'export -p'.
Even though bash (and dash) do not differ 'export' and 'export -p', that call
was clearly wrong as the -p was being passed as a parameter to /bin/sh, not
export.
Thanks to M. Warner Losh for bringing that
SVN commit 1190779 by rkcosta:
Properly quote the call to 'export -p'.
Even though bash (and dash) do not differ 'export' and 'export -p', that call
was clearly wrong as the -p was being passed as a parameter to /bin/sh, not
export.
Thanks to M. Warner Losh for bringing that up.
Will backport t
At Thu, 28 Oct 2010 01:10:03 -0200,
Raphael Kubo da Costa wrote:
> At Wed, 27 Oct 2010 20:51:17 -0600,
> M. Warner Losh wrote:
> > The reason this works with bash is that 'export' and 'export -p' produce
> > the same output. FreeBSD's 'export' produces different output than
> > 'export -p'. Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/27/2010 19:38, Raphael Kubo da Costa wrote:
> At Thu, 28 Oct 2010 14:59:37 -0400,
> Kris Moore wrote:
>> I've gone ahead and fixed the Xsession we ship in PC-BSD, however
>> this won't correct it for FreeBSD KDE users. This file is generated
>> w
On 10/27/2010 23:13, Bartosz Fabianowski wrote:
>> Do you know if (t)csh has no 'export' builtin and if /bin/sh should
>> really be identified as either of them?
>
> (t)csh uses 'setenv' in place of 'export'. (t)csh is not a Bourne
> shell. Relying on Bourne syntax is a typical Linuxism.
>
Typic
On 10/27/2010 20:30, Raphael Kubo da Costa wrote:
> At Wed, 27 Oct 2010 19:48:40 -0600,
> M. Warner Losh wrote:
>>On 10/27/2010 18:50, Raphael Kubo da Costa wrote:
>>> At Wed, 27 Oct 2010 18:23:57 -0600,
>>> M. Warner Losh wrote:
On 10/27/2010 18:20, Raphael Kubo da Costa wrote:
On 10/27/2010 18:50, Raphael Kubo da Costa wrote:
> At Wed, 27 Oct 2010 18:23:57 -0600,
> M. Warner Losh wrote:
>>On 10/27/2010 18:20, Raphael Kubo da Costa wrote:
>>> At Wed, 27 Oct 2010 17:39:58 -0600,
>>> M. Warner Losh wrote:
On 10/27/2010 17:38, Raphael Kubo da Costa wrote:
On 10/27/2010 18:20, Raphael Kubo da Costa wrote:
> At Wed, 27 Oct 2010 17:39:58 -0600,
> M. Warner Losh wrote:
>>On 10/27/2010 17:38, Raphael Kubo da Costa wrote:
>>> At Thu, 28 Oct 2010 14:59:37 -0400,
>>> Kris Moore wrote:
I've gone ahead and fixed the Xsession we ship in PC-BSD, howe
On 10/27/2010 17:38, Raphael Kubo da Costa wrote:
> At Thu, 28 Oct 2010 14:59:37 -0400,
> Kris Moore wrote:
>> I've gone ahead and fixed the Xsession we ship in PC-BSD, however
>> this won't correct it for FreeBSD KDE users. This file is generated
>> when the user runs "genkdmconf", and I confime
On 10/28/2010 12:59, Kris Moore wrote:
> On Wed, Oct 27, 2010 at 02:30:03PM -0600, M. Warner Losh wrote:
>>Greetings,
>>
>> I just spent a few days fighting ssh-agent. This normally trivial
>> affair has taken far too long. After much head scratching, I've tracked
>> the problem down.
>>
>>
Greetings,
I just spent a few days fighting ssh-agent. This normally trivial
affair has taken far too long. After much head scratching, I've tracked
the problem down.
FreeBSD's /bin/sh behaves differently than other systems. The commands:
sh -c export -p
and
sh -c "export -p"
are
Hello, kdevelop 4.1 was released two days ago. Hope to see updated port
soon.
Thanks in advance.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
12 matches
Mail list logo
