W. Stein wrote
> For Sage to run, I think all that's *needed* is:
> SAGE_ROOT/devel/sage/build/sage
So to do a thorough job I went on further with this:
Stripping by approach W.Stein
-----------------------------
Second Approach was like W. Stein suggested, I kept
SAGE_ROOT/devel/sage-main/build/sage and
SAGE_ROOT/devel/sage-main/clib
and moved other folders out
This gives a Size of 1239 M of the Sage-tree (unstripped binaries, no
double file fixing)
however, sage -testall starts to run and passes some doctests, but
soon fails.
...
The following tests failed:
/initrd/mnt/dev_save/Sage_Work/sage/devel/sage/doc/common # File not
found
/initrd/mnt/dev_save/Sage_Work/sage/devel/sage/doc/en # File not
found
/initrd/mnt/dev_save/Sage_Work/sage/devel/sage/doc/fr # File not
found
/initrd/mnt/dev_save/Sage_Work/sage/devel/sage/sage # File not found
sage -t -force_lib "devel/sagenb-main/sagenb/misc/sageinspect.py"
sage -t -force_lib "devel/sagenb-main/sagenb/misc/sphinxify.py"
Total time for all tests: 109.9 seconds
...
doc failures are clear, I moved them out, others are failures in
sagenb which I should not have touched - Hm, did I make an error?
Anyway!
I don't want to dig into that at the moment because I think everything
would be
just a (dirty?) hack and the preferred solution is a clean rebuild
according to the proposed solution with setuptools, or the other
method mentioned by Robert Bradshaw (build extensions inplace and put
devel/sage in python path).
Just a few more observations:
SAGE_ROOT/devel/sagenb_main
has about 36 MB of double files, i think the same arguments apply for
this directory tree.
If one would want to keep traceback cabapilities, would it be an
option to strip out comments of the
Python sources (but keep line numbering) or would this be a big
"No,No!" idea?
(of course with the commented python sources as separate package)
If I start with the result from -77 MB in the sfs size (with the
stripping mentioned above, and confirmed to work), there would be a
possibility to build a live CD with compilers and dev packages
included (under 700 MB), so cython could work out of the box. (Only
possible if size of the sage core remains somewhat stable in the next
releases)
I am pretty excited so far about the results :D, I hope it proofs
stable enough for use in the Live CD distribution.
emil
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
