#9433: Put more files under revision control.
--------------------------------------------+-------------------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-4.6.2
Component: distribution | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: Leif Leonhardy, Volker Braun | Merged:
Work_issues: |
--------------------------------------------+-------------------------------
Comment(by ddrake):
Replying to [comment:97 jdemeyer]:
> For this particular ticket, I feel that having a halfway-implemented
sage_root repository is strictly worse than having no sage_root repository
at all.
In what way is the SAGE_ROOT repo "halfway-implemented"? With these
scripts and patches, the repo will exist and work for upgrades and new
builds.
> The situation for merging SAGE_ROOT patches is already complicated
enough (but I can manage)
Maybe you can manage -- but there's plenty of evidence that other release
managers can't. Changing files in SAGE_ROOT currently takes a long time
and is an extremely brittle process; why continue in this way?
And even if there's no trouble actually changing files, we still have no
version control for our basic makefile, README, and executable script. The
only way to track changes is to download tarballs, unpack them, and
compare files. Think about it: neither the basic file with which we build
Sage (the makefile) nor the basic file with which one runs Sage
(SAGE_ROOT/sage) are under any version control! That is crazy. Imagine if
Firefox shipped with their "firefox" script not under version control.
> and I'm afraid the current patch on this ticket will make it only worse.
Right now to change the README:
* make a backup copy
* make your changes
* manually run {{{diff -u}}} to produce a patch
* upload ''both'' the new README and the patch to a ticket
* upon positive review, hope that the release manager replaces the
README file correctly and does {{{sage -sdist}}} in the right directory
With a SAGE_ROOT repo:
* use the same procedure that one uses in the Sage library to produce a
patch.
* release manager uses same procedure as for the Sage library to merge
the patch.
Perhaps it's only me, but the current situation seems far worse.
Please, let's create the SAGE_ROOT repo and argue about merging repos
after they actually exist.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9433#comment:99>
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.
