> On 31/12/2015, at 04:07, William Stein <[email protected]> wrote: > > why is there > both build and src/build?
Unfortunate naming perhaps. src/build is created by python when building sage itself. Not much you can do about that name. It is tempting to just nuke it but if you build with debug it will contain cython debugging info as well. I am betting the biggest culprit in src after build is doc. Currently vanilla sage builds every languages it supports but effectively only the English version is “complete” and presented to the user. You may be able to trim there. Did you build pdf documentation? It took an enormous amount of time for me to generate the Russian pdf because some of the fonts have to be generated on the fly for some reason and it took a *long* time to generate those fonts. Finally 6.3G in local seems excessive to me. I wonder if a few packages (probably optional ones) install a lot of files big or small. François -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
