> On 06/30/2010 02:05 AM, Dr. David Kirkby wrote: > > On 06/30/10 12:54 AM, Tim Daly wrote: > >> I'm surprised you don't use patch. > >> Mercurial can generate patches. > > > > That would only be ok at the point Mercurial is built, so might be > > tricky. > > $SAGE_ROOT/sage/spkg/standard/deps says... > > all: $(INST)/$(SAGE_SCRIPTS) $(INST)/$(SAGE) \ > $(INST)/$(EXAMPLES) $(INST)/$(GAP) $(INST)/$(SINGULAR) > ^^^^^^^^^^^^^^^^^^^ > $(INST)/$(MAXIMA) \ > $(INST)/$(G2RED) $(INST)/$(LCALC) $(INST)/$(SYMPOW) > $(INST)/$(MATPLOTLIB) \ > $(INST)/$(GFAN) $(INST)/$(ECM) $(INST)/$(TACHYON) \ > $(INST)/$(GIVARO) $(INST)/$(LINBOX) $(INST)/$(IML) \ > $(INST)/$(SYMMETRICA) $(INST)/$(POLYBORI) \ > $(INST)/$(GSL) $(INST)/$(GD) $(INST)/$(GDMODULE) \ > $(INST)/$(MERCURIAL) $(INST)/$(TWISTED) $(INST)/$(TWISTEDWEB2) \ > ^^^^^^^^^^^^^^^^^^^^ > > What about moving Mercurial some lines up? > > Then for the spkg, the src subdirectory would only contain a subdir > .hg and nothing else. This would contain all the sources of the > respective spkg which can then simply be extracted via 'hg update -C'. > Building this src subdir just means to say > hg init; hg add .; hg commit -m'singular-7.42.1' > and remove everything except .hg. > > Now one could, of course use a branch and put the patches already into > this .hg repo, but if you like to have them separate, put it into a > patches directory and then use 'hg import'. > > Why would one need an extra 'patch' program? > mercurial is a python program - python needs some patches, see a problem with using mercurial on its own?
Francois -- 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
