I created a binaries package for the use in a Live CD with the commands export SAGE_FAT_BINARY="yes" make ./sage -bdist x.y.z-fat
Testing seems ok (I am still unsure about sage -testall --optional, see http://groups.google.com/group/sage-support/browse_thread/thread/d3ffa3501849162b). Now I have a question: Is there any recommended procedere to make the resulting package smaller? I checked the package and e.g. found that dynamic libraries are not stripped. Also I found duplicate file entries in the directory tree. e.g. /devel/sage-main/build/lib.linux-i686-2.6 and /devel/sage-main/build/sage /devel/sage-main/sage contain lots of identical files. This are 100 MB+ directories, so no peanuts. /devel/sage-main/build/temp.linux-i686-2.6 contains object files of the libraries. I assume those directories are partly needed only for developement purposes, so maybe it would make sense to split tem into a seperate DEV package. I know almost nothing about the inner workings of sage, but clearly size was no restricting parameter in its design. (no critizism, also a valid approach) However there might be some situations, where a smaller size would open new possibilities. So let me ask if there are any ideas around to reduce the size of final binaries (remove possibly unneeded files, strip/upx executeables) or if such approaches are vain because it is not possible to shrink the binaries? Thanks in advance for advice 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
