After being away from Julia and the community for a couple of months, I started updating my Julia installations today in order to test some of my packages and make sure they’re ready for 0.5, and I started getting warnings about disk usage. Since I’m dual-booting Ubuntu and Windows on a laptop with only about 120GB SSD space, disk space is precious and every GB counts.
I have two parallel installations of Julia on my laptop, both built from source - the release-0.4 branch and the release-0.5 branch (this folder used to contain the master branch, but I checked out release-0.5 today). After building with make (preceded by make cleanall in the 0.5 folder) and pruning everything indicated by git status to be added (mostly tarballs and a couple of repos inside deps/) I now have the following status: /opt/julia-0.4 release-0.4 $ git status On branch release-0.4 Your branch is up-to-date with 'origin/release-0.4'. nothing to commit, working directory clean /opt/julia-0.5 release-0.5 $ git status On branch release-0.5 Your branch is up-to-date with 'origin/release-0.5'. nothing to commit, working directory clean /opt $ du -hd1 | sort -hr 6,8G . 4,0G ./julia-0.5 2,3G ./julia-0.4 # smaller stuff omitted Both instances of Julia are runnable, so I don’t think I deleted something I shouldn’t have in either folder. What has changed to make Julia 0.5 so big? Are there any build artifacts I can/should prune to reduce this footprint? // T
