#14372: Document ccache better in developer guide
--------------------------------------+--------------------------
Reporter: robertwb | Owner: tbd
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-6.3
Component: packages: standard | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------------+--------------------------
Comment (by leif):
Replying to [comment:34 nbruin]:
> Replying to [comment:33 kcrisman]:
> > Though I don't think it should be in binaries anyway. On a small USB
key and some other situations 4 GB is quite a bit.
> The 4GB is the default cache size. It would sit in the user homedir
Which in many cases would be the wrong place.
> and only gets filled if something is actually compiled (which would fail
in a binary distribution, I think).
While it only gets filled upon compilation, `sage -b` is sufficient, as is
the installation of an optional spkg in many if not most cases. The only
difference of bdists is that they don't come with ''upstream'' source code
(i.e., spkgs, or tarballs in `upstream/`.)
> So, shipping ccache with a binary would be useless, but it wouldn't
particularly use 4GB anywhere either.
See above.
--
Ticket URL: <http://trac.sagemath.org/ticket/14372#comment:35>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
