On Tuesday, February 26, 2013 3:44:38 PM UTC-8, JMH wrote:
>
> Hi,
>
> On Wednesday, February 27, 2013 12:03:40 AM UTC+1, leif wrote:
>>
>> (...)
>> ... and if you need multiple versions of the "same" package(s) installed
>> at the same time (but only one of them when running Sage), can't you
>> just create symbolic links foo->foo-version-x.y.z accordingly (in the
>> "usual" directories mentioned above) before starting Sage?
>> (...)
>>
>
> That's not really a correct statement.
> I need several versions of the same package and all of them need to be
> operational at the same time.
> That means, I open two / three terminal windows and in each of them I
> start the same "sage" executable but each session should use a different
> version of my additional package ... something like:
> export CURRENT_VERSION="in_this_window_use_that_version"; ./sage
> That's why I cannot "install" my binaries (nor make symbolic links) into
> the standard $SAGE_ROOT/local/{bin|lib|...} subdirectories.
> And that's why I need a mechanism of initialization at "run-time"
> (modification of "PATH", "LD_LIBRARY_PATH", "PYTHONPATH", ..)
>
What if, while you're running Sage, you modify os.environ['PATH'], etc.?
Will that accomplish what you want?
--
John
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
