What can I delete?
So I've compiled sage from sources. The sage folder is now 3Gb. I guess I've no need for some files... What can I delete? Is there any reason I should not delete these things?
So I've compiled sage from sources. The sage folder is now 3Gb. I guess I've no need for some files... What can I delete? Is there any reason I should not delete these things?
In principle, you should be able to type make micro_release
, but this may be broken, depending on your platform. (I think that if it's broken, it will still result in a working Sage installation, just one that isn't as small as it should be.)
When you run sage micro_release
, it runs the script local/bin/sage-micro-release
, which among other things removes the directories devel/sage/build/temp.*
and devel/sage/build/lib.*
. You should be able to delete those safely by hand, if the script fails.
You can also safely remove the directory spkg/logs/
. If you're sure you're not going to need to reinstall anything, you could remove spkg/standard/
.
For updates, I would try `sage --upgrade`, or `sage --upgrade URL`. I don't know how updating interacts with removing these folders.
You should be able to delete the devel
folder, assuming you don't want to re-compile or get involved in Sage development.
Yes, docs are in devel. I wouldn't delete all of devel.
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2012-06-08 09:29:41 +0200
Seen: 938 times
Last updated: Jun 08 '12
can i compile sage with the Intel's compilers?
building sage-4.6.1 from source fails because of missing fortran
Graph minor code (too slow in certain situations) Sage 4.6
Upgrade sage: build from sources?
Error in looking at source code
Compiling SAGE 5.5 -- Matplot Lib Fails to find Numpy
Compiling problem after sudden shutdown