Re: POSIX replacement for bash's “export -n” ?

2010-07-12 Thread Chris Jackson
Charles Plessy wrote: Hello everybody, In one of the packages I maintain, building fails when the default shell is /bin/dash because of an “export -n” command that was not found by checkbashisms (probably because it was hidden in a Perl script). I would like to send a patch Upstream, but have

Re: POSIX replacement for bash's “export -n” ?

2010-07-12 Thread Chris Jackson
Chris Jackson wrote: There really doesn't seem to be a way. I can only suggest: * bolt those comands up into an unexport function (not pretty; make your BAR local and you don't need to subsequently unset it) For reference, this seems to work: unexport() { local unexport_var=`eval

Re: POSIX replacement for bash's “export -n” ?

2010-07-12 Thread Charles Plessy
Le Mon, Jul 12, 2010 at 08:56:25AM +0100, Chris Jackson a écrit : I would like to send a patch Upstream, but have not found a drop-in replacement for this command, apart from someghing ugly like: BAR=$FOO ; unset FOO ; FOO=$BAR ; unset BAR to replace ‘export -n FOO’. * perhaps you can

Re: POSIX replacement for bash's “export -n” ?

2010-07-12 Thread Peter Pentchev
On Mon, Jul 12, 2010 at 08:56:55PM +0900, Charles Plessy wrote: Le Mon, Jul 12, 2010 at 08:56:25AM +0100, Chris Jackson a écrit : I would like to send a patch Upstream, but have not found a drop-in replacement for this command, apart from someghing ugly like: BAR=$FOO ; unset FOO ;

Re: POSIX replacement for bash's “export -n” ?

2010-07-12 Thread Charles Plessy
Le Mon, Jul 12, 2010 at 03:01:35PM +0300, Peter Pentchev a écrit : On Mon, Jul 12, 2010 at 08:56:55PM +0900, Charles Plessy wrote: open (WOSSNAME, export -n EMBOSS_ACDCOMMANDLINE;wossname -alpha -auto|) || die Cannot run wossname; by the following line: open (WOSSNAME,

POSIX replacement for bash's “export -n” ?

2010-07-11 Thread Charles Plessy
Hello everybody, In one of the packages I maintain, building fails when the default shell is /bin/dash because of an “export -n” command that was not found by checkbashisms (probably because it was hidden in a Perl script). I would like to send a patch Upstream, but have not found a drop-in