My hard disk was nearly full and I couldn't think why ... until I looked into binary-pkg. There was something like 39G in there! And I'm not counting the dist/ directory. The source directory alone had 7.6G. I'm not aware that the Sage source is quite THAT big :-)
The only thing I use this for is making Sage binaries on my now-oldish Mac laptop for upload to sagemath.org. But it basically seems to keep everything ever, rather than 'upgrading' the way my Sage directory for my "work use" Sage does (git pull and make etc.). I'm not criticizing binary-pkg per se; it seems to have solved a difficult problem for Mac in particular. But I do wonder whether there might be a simple fix to why there is so much in source/ and staging/ (if it's staged, shouldn't it be removed at the end?). For instance, maybe the simple fix is that this has been fixed already, but I didn't know I should do a git pull! (That kind of thing probably should be announced here and/or sage-release if necessary.) Thanks for any thoughts, looking forward to using it again quite soon for the next Sage release! - kcrisman -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
