On 25 Aug., 16:51, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2011-08-25 14:40, leif wrote:
>
> > What I can definitely say is that Sage 4.7.1.rc2's hg cannot handle
> > Sage 4.7.2.alpha2's root repo, which *will* break upgrading...
>
> If this is true, then #10594 needs work!
According to deps, it /should/^TM work, since we have:
# the spkg-install file for the root repo uses many 'hg' commands, so
# build mercurial first.
$(INST)/$(SAGE_ROOT_REPO): $(BASE) $(INST)/$(MERCURIAL) $(INST)/$
(PATCH)
$(INSTALL) "$(SAGE_SPKG) $(SAGE_ROOT_REPO) 2>&1" "tee -a $
(SAGE_LOGS)/$(SAGE_ROOT_REPO).log"
I haven't checked yet whether the scripts should also depend on
Mercurial for that reason; extcode already does.
The rationale used to be that Mercurial is available in upgrades, and
especially if there are already repos to upgrade, assuming a[ny]
previous version will be able to handle repos shipped in upgraded
packages as well.
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
