Hi,
well, in general I could imagine that my "extra" package gets installed
into the "standard" Sage subdirectories (so that there would be no need to
set "PATH", "LD_LIBRARY_PATH", "PYTHONPATH", ...).
However, this is not really the desired situation.
In fact I need to make sure that I can have
On 2013-02-24 20:57, JMH wrote:
> Also, if you do not think that I should modify the standard "sage-env"
> script, how can I "register" my library in a different way?
> Before I source my "setup" shell script (bash), I need all Sage related
> variables to be set, so the end of the standard "sage-en
