Refereeing #9967 has turned into implementing some of its key features,
and I need to know more about how the Sage library is built by
SAGE_ROOT/devel/sage/setup.py.

I know that it creates a symlink from
SAGE_ROOT/local/lib/python/site-packages to a build directory. What I
eventually want is for the build process to not create a symlink and go
straight to that directory, but in the meantime, I see that
SAGE_ROOT/devel/sage/build has three directories which each seem to
include a copy of the Sage library:

dr...@sagenb:~/s/sage-4.6/devel/sage-main/build$ du -s -h *
147M    lib.linux-x86_64-2.6
182M    sage
168M    temp.linux-x86_64-2.6

They seem to be independent copies. Why are they there? Which one is the
"real" one that's used when Sage is running?

(And, most importantly for #9967, how do we get setup.py to use the
correct directory directly? Changing SITE_PACKAGES in setup.py didn't
seem to work.)

Thanks,

Dan

--
---  Dan Drake
-----  http://mathsci.kaist.ac.kr/~drake
-------

Attachment: signature.asc
Description: Digital signature

Reply via email to