#9433: Put more files under revision control.
------------------------------+---------------------------------------------
Reporter: jhpalmieri | Owner: tbd
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: distribution | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: Leif Leonhardy | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by jhpalmieri):
Replying to [comment:68 leif]:
Downloading these various files in sage-update seems to at least partly
defeat the purpose of the new repo, but anyway.
> Replying to [comment:67 jhpalmieri]:
> > I don't want to put it [deps] because in a non-upgrade, it's already
installed as part of the download.
>
> Well, then `hg pull` would simply be a no-op. But we should check the
exit codes of the commands in `root-spkg-install` (`hg` and `cp`) anyway.
If we put it in deps, I guess it gets installed at the end? I was tempted
to make it part of BASE, but then during an upgrade, any changes to the
Sage root repo would mean that everything would be rebuilt, which would be
annoying. The only issue is if there is an upgrade to a script like
"pipestatus" which is in the root repo, is used in the upgrade process,
and is not downloaded in sage-update.
> P.S.: I wonder if the presence of `$SAGE_ROOT/.hg` guarantees us a
functional Mercurial... ;-)
I think I'll switch to running "hg verify".
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9433#comment:69>
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.
