Hi,
I've got the following problem.
I am building an external library which I want to add to Sage (via some
python bindings).
I put the binaries into the "${SAGE_LOCAL}" chain.
In order to use that library, some environment variables need to be set and
a "setup" shell script (bash) needs to be sourced.
So, I added some lines in the end of the standard "spkg/bin/sage-env"
script.
This works well, except that when I try to create a new "binary
distribution" ("./sage --bdist ..."), the "sage-env" script in that new
tarball is the "original" one, without my modifications.
Could you, please, tell me what do I need to do in order to get my
modifications automatically included?
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", ...).
Thanks in advance,
Best regards,
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.
