#13032: Add ccache as an optional spkg
-------------------------------------+--------------------------------------
Reporter: rohana | Owner: GeorgSWeber
Type: enhancement | Status: closed
Priority: major | Milestone: sage-5.6
Component: optional packages | Resolution: fixed
Keywords: sd40.5 | Work issues:
Report Upstream: N/A | Reviewers: Punarbasu Purkayastha
Authors: R. Andrew Ohana | Merged in: sage-5.6.beta2
Dependencies: | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by kini):
>Probably Sage's readline uses non-Sage-specific configuration files
(`$HOME/.inputrc`).
Does Sage ''change'' `~/.inputrc` or just read it? Sage of course reads
tons of files all over the system. An example of another dotfile in `~`
that Sage (or Sage's Mercurial anyway) reads is `~/.hgrc`. But it will
''change'' `~/.ccache`.
>Of course it's not much burden for me, but what about other people in the
same situation?
As I said, we can print a note at the end of the SPKG installation
process, or otherwise document it. I suspect that most users will not mind
that the ccache directory `~/.sage/ccache` is used, and if they do, it is
probably because they are already running ccache on their system and want
to consolidate the cache directories together, so they're probably savvy
enough to make a symlink.
>This patch changes the ccache directory and the cache size ''behind
people's back'' if they were using system ccache before.
Sage installs another copy of Python on the system "behind people's back"
as well and nobody complains (or at least we don't listen to such
complaints). I don't see the problem.
Also, maybe I am misunderstanding something. Are you saying that
installing this SPKG into Sage will change the behavior of the system
ccache running independently of Sage?
>Which is a problem because ...........?
For one thing, it means more detritus around the system to clean up if you
want to remove Sage from your system. And very large unwanted detritus at
that, if the user doesn't have a system ccache. Of course, it's an
optional package, so we can assume the user at least knows they have
installed the ccache SPKG, but most users would expect that they can
completely eradicate Sage and all its artifacts by deleting the Sage
directory and `$DOT_SAGE`.
Also, this kind of lack of compartmentalization just seems unhygienic. I
kind of don't like the idea of Sage interacting with and modifying data
that belongs to other programs which I've installed systemwide. I like
that Sage is a sandbox mini-distribution of software which is self-
contained. (Or, at least that's the paradigm the official Sage
distribution has conformed to so far, sage-on-gentoo and sage-on-debian
notwithstanding.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13032#comment:63>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
