Quoting "Jason R. Mastaler" <[EMAIL PROTECTED]>: > I dunno, perhaps I'll look into whether it's possible to pass in an > environment variable to override the /usr/bin/python2.3 requirement or > something.
How about replacing all the binaries in .../tmda/bin with shell scripts. Each shell script can calculate which directory it's in (hackery on $0 if I remember from when I did this with Perl scripts on Solaris a number of years ago), then run "$TMDADIR/bin/python $TMDADIR/bin/$binaryname.py $*". This means TMDA binaries will always use the python executable in the TMDA bin directory - which will be a sym/hard-link to the desired Python interpreter. Of course, this then means TMDA depends on some shell interpreter, but if a Bourne-like script was used, this probably would be easy to satisfy! -- Stephen Warren, Software Engineer, Parama Networks, San Jose, CA [EMAIL PROTECTED] http://www.wwwdotorg.org/ _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
