ASKSAGE: Sage Q&A Forum - Individual question feedhttp://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Fri, 02 Aug 2019 14:44:48 -0500I just built a Sage system. What files may I delete with impunity?http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/I have just built Sage 7.6 on an Apple iMac 8,1 running OS X version 10.11.6. I started with a download of a compressed source distribution from the Sage github repository (without cloning the repository itself, since I don't plan to contribute any development ideas or comments for awhile). Doctesting went very well, with only two failed tests out of the entire suite:
sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
I also downloaded the equivalent binary distribution and doctested that, obtaining these results:
sage -t src/sage/calculus/calculus.py # 1 doctest failed
sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/graphs/digraph_generators.py # 3 doctests failed
sage -t src/sage/graphs/graph_generators.py # 5 doctests failed
sage -t src/sage/graphs/hypergraph_generators.py # 7 doctests failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
sage -t src/sage/tests/cmdline.py # Timed out after testing finished
I did expect my own build to do better, but the installation I ended up with is fully 2 GB larger than what came in the binary distribution. Much (more than 1/3) of the overage is in a directory
../sage-7.6/local/share/doc/sage/doctrees
which is not present in the binary distribution, and I assume it is only of interest to developers. Is that correct? I will trim my build by also removing two large files
../sage-7.6/src/build/temp.macosx.10.9...
../sage-7.6/src/build/lib.macosx.10.9...
but keep my log and upstream files in case I want to review the build or look at the sources. All this is pending any further advice I get in the next few days about files that are generally only of interest to developers.Fri, 02 Aug 2019 14:03:57 -0500http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/Comment by dyne2meter for <p>I have just built Sage 7.6 on an Apple iMac 8,1 running OS X version 10.11.6. I started with a download of a compressed source distribution from the Sage github repository (without cloning the repository itself, since I don't plan to contribute any development ideas or comments for awhile). Doctesting went very well, with only two failed tests out of the entire suite:</p>
<pre><code>sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
</code></pre>
<p>I also downloaded the equivalent binary distribution and doctested that, obtaining these results:</p>
<pre><code>sage -t src/sage/calculus/calculus.py # 1 doctest failed
sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/graphs/digraph_generators.py # 3 doctests failed
sage -t src/sage/graphs/graph_generators.py # 5 doctests failed
sage -t src/sage/graphs/hypergraph_generators.py # 7 doctests failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
sage -t src/sage/tests/cmdline.py # Timed out after testing finished
</code></pre>
<p>I did expect my own build to do better, but the installation I ended up with is fully 2 GB larger than what came in the binary distribution. Much (more than 1/3) of the overage is in a directory</p>
<pre><code>../sage-7.6/local/share/doc/sage/doctrees
</code></pre>
<p>which is not present in the binary distribution, and I assume it is only of interest to developers. Is that correct? I will trim my build by also removing two large files</p>
<pre><code>../sage-7.6/src/build/temp.macosx.10.9...
../sage-7.6/src/build/lib.macosx.10.9...
</code></pre>
<p>but keep my log and upstream files in case I want to review the build or look at the sources. All this is pending any further advice I get in the next few days about files that are generally only of interest to developers.</p>
http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/?comment=47355#post-id-47355Thanks for your replies! I see that in the binary downloads there is an 8.6 release that is listed for my system, Mac OS X 10.11. That would give me the benefit of subsequent bug fixes.
I must agree that sage-7.6 is an old release, but my hardware is much, much older! I will give it a try on the 8.6 build after I begin to learn something substantive about using Sage -- intro linear algebra is my current study. I will certainly report back, here, if I experience problems beyond doc testing.
I'm inclined immediately to accept your answer, given below. Am I the only one who can do that?Fri, 02 Aug 2019 14:44:48 -0500http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/?comment=47355#post-id-47355Comment by John Palmieri for <p>I have just built Sage 7.6 on an Apple iMac 8,1 running OS X version 10.11.6. I started with a download of a compressed source distribution from the Sage github repository (without cloning the repository itself, since I don't plan to contribute any development ideas or comments for awhile). Doctesting went very well, with only two failed tests out of the entire suite:</p>
<pre><code>sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
</code></pre>
<p>I also downloaded the equivalent binary distribution and doctested that, obtaining these results:</p>
<pre><code>sage -t src/sage/calculus/calculus.py # 1 doctest failed
sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/graphs/digraph_generators.py # 3 doctests failed
sage -t src/sage/graphs/graph_generators.py # 5 doctests failed
sage -t src/sage/graphs/hypergraph_generators.py # 7 doctests failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
sage -t src/sage/tests/cmdline.py # Timed out after testing finished
</code></pre>
<p>I did expect my own build to do better, but the installation I ended up with is fully 2 GB larger than what came in the binary distribution. Much (more than 1/3) of the overage is in a directory</p>
<pre><code>../sage-7.6/local/share/doc/sage/doctrees
</code></pre>
<p>which is not present in the binary distribution, and I assume it is only of interest to developers. Is that correct? I will trim my build by also removing two large files</p>
<pre><code>../sage-7.6/src/build/temp.macosx.10.9...
../sage-7.6/src/build/lib.macosx.10.9...
</code></pre>
<p>but keep my log and upstream files in case I want to review the build or look at the sources. All this is pending any further advice I get in the next few days about files that are generally only of interest to developers.</p>
http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/?comment=47354#post-id-47354Why version 7.6? That's pretty old. Did more recent versions fail for you?Fri, 02 Aug 2019 14:25:56 -0500http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/?comment=47354#post-id-47354Answer by John Palmieri for <p>I have just built Sage 7.6 on an Apple iMac 8,1 running OS X version 10.11.6. I started with a download of a compressed source distribution from the Sage github repository (without cloning the repository itself, since I don't plan to contribute any development ideas or comments for awhile). Doctesting went very well, with only two failed tests out of the entire suite:</p>
<pre><code>sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
</code></pre>
<p>I also downloaded the equivalent binary distribution and doctested that, obtaining these results:</p>
<pre><code>sage -t src/sage/calculus/calculus.py # 1 doctest failed
sage -t src/sage/doctest/test.py # 1 doctest failed
sage -t src/sage/graphs/digraph_generators.py # 3 doctests failed
sage -t src/sage/graphs/graph_generators.py # 5 doctests failed
sage -t src/sage/graphs/hypergraph_generators.py # 7 doctests failed
sage -t src/sage/modules/vector_rational_dense.pyx # 1 doctest failed
sage -t src/sage/tests/cmdline.py # Timed out after testing finished
</code></pre>
<p>I did expect my own build to do better, but the installation I ended up with is fully 2 GB larger than what came in the binary distribution. Much (more than 1/3) of the overage is in a directory</p>
<pre><code>../sage-7.6/local/share/doc/sage/doctrees
</code></pre>
<p>which is not present in the binary distribution, and I assume it is only of interest to developers. Is that correct? I will trim my build by also removing two large files</p>
<pre><code>../sage-7.6/src/build/temp.macosx.10.9...
../sage-7.6/src/build/lib.macosx.10.9...
</code></pre>
<p>but keep my log and upstream files in case I want to review the build or look at the sources. All this is pending any further advice I get in the next few days about files that are generally only of interest to developers.</p>
http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/?answer=47353#post-id-47353`make clean` and `make misc-clean` are safe, although the second of these will remove log files. `make micro_release` should also be safe, although it will remove all of the built documentation. Removing everything in `local/share/doc/sage/` except for `html` and (if present) `pdf` should be safe. Removing `upstream` will still allow Sage to run, but you would then need to download a lot of tar files if you ever wanted to rebuild it.Fri, 02 Aug 2019 14:25:30 -0500http://ask.sagemath.org/question/47352/i-just-built-a-sage-system-what-files-may-i-delete-with-impunity/?answer=47353#post-id-47353