#9433: Put more files under revision control.
--------------------------------------------+-------------------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status: needs_review
Priority: blocker | Milestone: sage-4.7
Component: distribution | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: Leif Leonhardy, Volker Braun | Merged:
Work_issues: |
--------------------------------------------+-------------------------------
Changes (by jhpalmieri):
* status: needs_work => needs_review
Comment:
I don't really understand this complaint. After all, Sage is distributed
with a version of Mercurial, and it is completely reasonable to require
that version for repositories which are part of Sage. It's easy enough to
type "sage -hg" instead of "hg", or make an alias, or put the Sage version
of hg in your $PATH. I think this is more a problem with Mercurial -- why
is it not backwards compatible? Who merged this version of Mercurial into
Sage? Did the spkg maintainers or release manager notice or discuss this
incompatibility issue?
Also, if you're going to start inventing rules about how an spkg should be
prepared, you might consider putting those rules in the developer's guide,
and perhaps discussing them and getting approval for them on sage-devel
before imposing them.
We can add {{{--config format.dotencode=0}}} at various places in sage-
sdist and sage-make_devel_packages, and I'm attaching a new version of the
scripts patch to do this, but this is not a viable long-term solution: the
version requirements of Mercurial for anyone who wants to make a new spkg
for Sage need to be made public, not imposed at anyone's whim.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9433#comment:134>
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.
