Has guile version check changed?

[Geert Janssens]

I haven't followed the complete discussion on this topic.

However the 'env' issue caught my attention.

$ env FOO=bar echo $FOO
won't work. On the other hand
$ export FOO=bar; echo $FOO
will, or in csh
% set env FOO=bar; echo $FOO

The trick is to set the environment before the echo statement gets evaluated.

If you can't split the command into two subcommands (I'm not sure with the 
guile16-build command), you could also delay the evaluation by executing the 
echo command in a subshell. For example:
$ env FOO=bar sh -c 'echo $FOO'
Note the single quotes: they prevent $FOO being evaluated by the original 
shell which is used to evoke env.

Just my 2c.

Cheers,

Geert

On Sunday 22 October 2006 01:11, Chris Shoemaker wrote:
> On Sat, Oct 21, 2006 at 06:29:53PM -0400, Derek Atkins wrote:
> > Actually, 'env' does export to children.  That's the whole point of
> > 'env'.
> >
> > "man env" for more info.
>
> Doh.  Of course it does.  However...
>
> $ env FOO=bar echo $FOO
>
> will _not_ show the "bar", but for a totally different reason.  The
> variable substitution will occur _before_ env is executed, so:
>
> % guile16-build env PATH=/opt/bin:$PATH echo $PATH
>
> is just a really dumb test.  Looks like David figured things out in
> spite of my help, though. :)
>
> -chris
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel