On Tue, Feb 04, 2014 at 12:57:04PM -0800, William Stein wrote: > It would be cool if there were a make target that did all of this..., > e.g., "make cache-clean" since it is not at clear from the name that > "upstream" is a cache directory that can be safely deleted, especially > given that in the previous version of sage it (=spkg/standard/) had > much the same content, and deleting it would be devastating.
+1 ! Could someone tell what other directories/files can be removed without any loss. I guess the following are OK, but i am not sure: - src/doc/output/doctrees - src/doc/output/inventory Also, the Makefile has a 'micro_release' target that strips all binaries. - To what extend does this affect the build ? - It is still possible to use/develop Sage without any problem after such a strip ? - Are some Sage debugging tool that need unstripped binaries ? Now, from a non-developper point of view (i mean someone that will not touch the sources, but still want to be able do do 'sage -i' to install optional packages), what more can be removed ? - .git - sage/local/libexec/git-core - sage/local/share/git* - what else ? Doing all that, i was able to build Sage in a 284M squashfs file, which is not bad if we want to have live CD back (or smaller live USB). Ciao, Thierry -- 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. For more options, visit https://groups.google.com/groups/opt_out.
