On Tue, 16 Feb 2010 12:38:59 Robert Bradshaw wrote: > Another issue with the piecemeal approach is that upgrading a > component could suddenly cause Sage to break. Have you given any > thought to how you will handle this? > Kind of. We can have several versions of the same package in tree. We can even make some major version of some package to coexist if absolutely necessary (although it is usually avoided as much as possible). We can enforce a particular version of a package and keep it around if required. We already have to do that with linbox/givaro. The big problem are with very old packages that have been dropped of the tree networx, cvxopt and sqlalchemy being the main culprits on that account at the moment. We could dig the old version or make one but they really should move forward even if we have to patch...
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
