> I think that's definitely something we should look into! Could you > post a bash script? What somebody also has to check is, if it is still > possible to do development. i.e. apply some patches, changing cython > files, sage -b and then checking it again.
Hi Harald, this is the procedure suggested by Volker Braun, i.e. just replace all double file occurrences with hardlinks + strip --strip-unneeded for all binaries and libraries. All python sources are left in the tree, so traceback works. I have never done sage -b or any development in sage itself, so it's better somebody else checks this. I am not so good at bash scripting, but it is basically just the above 4 commands: (put the fslint scripts in the path, actually only the script findup is needed ) So the prototype is (untested): #!/bin/sh cd SAGE_ROOT findup -m . find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null and for me in the Live CD distribution as an addition to create an sfs package (squashed file system): cd .. dir2sfs SAGE_ROOT (basically command mksquashfs SAGE_ROOT) whole procedure takes 5 - 10 minutes for me on a vanilla PC. Gruesse nach Wien 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
