Re: [ferret_users] run ferret and pyferret together

[Ryo Furue <furue@xxxxxxxxxx>]

Hi Patrick,

> I would like to work with both tools for testing purposes.
> But after having sourced the 2 different environnements,
> I get some environment variables conflicts that
> I do understand but don't know how to solve properly.

I don't set env.vars. globally but use my own wrapper script like this:

    #!/bin/sh
    FER_DIR="/usr/local/ferret"
    export FER_DSETS="$FER_DIR"
    export FER_FONTS="${FER_DIR}/ppl/fonts"
    export PLOTFONTS="${FER_DIR}/ppl/fonts"
    # . . . after setting all env.vars. . . .
    exec "$FER_DIR/bin/ferret_v6.94" "$@"

and call this script "ferret".  Then you don't have to set env.vars. any longer.

I don't use pyferret, but you can write two scripts like this, one for
ferret and the other for pyferret, their env.vars. not conflicting.

Instead of writing scripts like the above, you may be get by with

   #!/bin/sh
   source /usr/local/ferret/bin/ferret_paths.sh
   exec /usr/local/ferret/bin/ferret_v6.94 "$@"

(untested).

Cheers,

Ryo