#10988: Make sage-update more developer-friendly
-----------------------+----------------------------------------------------
Reporter: kini | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-4.7
Component: scripts | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
The $SAGE_ROOT/local/bin/sage-update script should allow upgrading between
alphas.
There should be a way to tell it to avoid pointless merges between
released alphas and their equivalent, build-milestone alphas inside newer
alphas, for those of us who don't want or need anything to be merged.
Since alphas are currently released based on the previous stable release
rather than the previous alpha, there could be an option (maybe even a
default) to strip the old alpha's branch from the stable version after
installing the new alpha. There is a general procedure I currently follow
to move all my patches from old alphas to new alphas which could be
automated as well.
I marked this as a defect as I think it seems reasonable to expect `sage
-upgrade` to be able to do stuff like this (or at least be usable for
upgrading between alphas), but if you disagree, feel free to change it to
a feature request.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10988>
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.
