[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pre-inst-guile
From: |
Thien-Thi Nguyen |
Subject: |
Re: pre-inst-guile |
Date: |
Mon, 04 Mar 2002 15:36:34 -0800 |
From: Rob Browning <address@hidden>
Date: Mon, 04 Mar 2002 17:19:04 -0600
OK, that seems pretty good for this case, though it wouldn't handle a
script that has sub-invocations of guile. I suppose we can cross that
bridge when (if) we come to it :>
the scripts/foo programs use GUILE env var for this purpose, q.v.
Come to think of it, we could probably cross that bridge just fine by
doing something like this during make check (or make):
cd test-suite
mkdir test-bins
cd test-bins
ln -s ${top_srcdir}/pre-inst-guile ./guile
PATH=`pwd`:${PATH} ./guile -e main -s ${top_srcdir}/some/script-to-test
basically linking pre-inst-guile as guile in some temp dir and
putting that dir first in the path. Then even sub-execs of guile (as
long as they weren't fully qualified) would work fine. Of course
that leaves unanswered the question of how often they wouldn't be
fully qualified. sub #! guile scripts would still fail.
probably using GUILE env var convention would work. instead of "guile",
use "${GUILE-guile}".
However if we switched our scripts to use
#!/usr/bin/env guile
we'd be fine, which is how the new SRFI wants you to invoke other
things, but I'm not what if any issues there might be regarding the
use of env in general...
unfortunately this doesn't support passing args to guile.
thi