On Feb 24, 11:57 am, JMH <jacek.m.holec...@gmail.com> 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-env" script seemed a > good idea to me (I need to add some entries into "PATH", "LD_LIBRARY_PATH", > "PYTHONPATH", ...).
An unattractive feature of adding more infrastructure to modify the environment is that sage goes even more in the direction of being a "distribution" rather than a software package. Some people still have faint hopes that it would be doable to chop sage up into components that would fit in a more standard software packaging system. For variables that you mention: - instead of adding to PATH, you could add your executables to $SAGE_ROOT/local/bin - Modifying LD_LIBRARY_PATH is frowned upon. It's supposed to be a last resort for the end user to change things up if all else fails. Sage does so because it creates its own little world, but within that world you have the usual tools available. Can't you just add your libraries to (a subdir of) $SAGE_ROOT/local/lib ? - can't you just install your python packages in the location that sage Python already looks in? The key is: normal software installation doesn't require changing these variable names. Each of those are user convenience variables to hack around system configuration problems. Probably you can accomplish what you need without touching these variables. -- 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.
