#12342: things I don't like about the json <--> hg conversion code
----------------------------+-----------------------------------------------
Reporter: was | Owner: tbd
Type: defect | Status: new
Priority: critical | Milestone: sage-5.0
Component: distribution | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
----------------------------+-----------------------------------------------
Comment(by was):
Hi,
I wrote this script hg_json, which does something very useful standalone
-- it swaps between having a .hg directory and having a .hg.json file.
The hard work is all done by the code you had already written.
Thoughts?
I hope not to work much more on this ticket, and that you (Kini) could
somehow finish it. We need to come up with a workflow. Maybe can have an
option to sdist, e.g.,
{{{
sage -sdist --paranoid
}}}
which replaces all .hg repos by .hg.json files... for now (maybe removes
binaries, e.g., that gfortran spkg), and when someday we switch to git, it
will do the analogous thing. Then Sage's own build system will be smart
enough to deal with the .hg.json files, so that a tarball built using
--paranoid will build fine with *no* further changes. Now, *that* would
be nice, right?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12342#comment:5>
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.