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 several versions of my "extra"
packages available simultaneously.
So, I install every version of my package into a separate chain of version
specific subdirectories (somewhere in "${SAGE_LOCAL}").
One is expected to "select" the exact version that one wants to use during
the "current" session using something like "export MyVersion="SomeVersion";
./sage" and then the "sage-env" script is expected to take care that the
requested version gets "loaded".
Moreover, some "extra" parts use/need some "environment variables", so I
need to make sure that they exist and that they point to "relevant" places.
So, I really need some kind of a "run-time" package initialization.
It seems to me that this is not foreseen now.
I think I would like to add a "general purpose" mechanism of "run-time"
package initialization into the standard "sage-env" script.
Will you incorporate such a mechanism into the "official" source code?
If yes, I could send you a "patch file".
Jacek.
--
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.
