One unmentioned feature of a git-based Sage archive is the ability to pull a guaranteed-correct tree from history. This is not possible using CVS or SVN. I am not sure about bzr or hg.
Suppose you work on Sage-3.0.2 and it has an spkg, say SymPy at 3.3. Suppose both Sage-3.0.2 and SymPy are held in different git repos somewhere on the net (e.g Sage in sagemath.org, sympy in sympy.org) Now suppose the world moves on to Sage-3.1 and SymPy goes to 4.0 You can set up Sage so that if a user does a git-pull on Sage-3.0.2 the "make" procedure can git-pull the correct tree (3.3) from sympy. Since the git repo tree nodes are all uniquely labelled by a 40 bit hash code you can be certain you got exactly the right sympy build. The advantage is that you would no longer have to have any spkg code that contained sympy. And if I don't use sympy I don't need to download it. Note that, in general, I very much like the fact that I only do one tarball download, type "make" and it "just works". But the latest DCVS tools support functionality that was not possible using CVS/SVN. Tim --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
