On Sat, Nov 22, 2008 at 6:46 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Nov 22, 6:43 pm, Ronan Paixão <[EMAIL PROTECTED]> wrote: > > <SNIP> > >> > Sure, if there actually is somebody out there who has ever used the >> > spkg/archive. >> > I'm kind of guessing nobody has ever used it, in which case it seems >> > completely >> > pointless to support. >> >> > William >> >> A compromise option would be to delete all versions except the one >> that's being upgraded from, so that archive/ only has one version. >> >> But even that may be pointless, since having previous versions is the >> whole point of using a version control system, and sage uses mercurial, >> which should allow to revert to old spkgs. > > Nope, that won't work. Setting aside a few exceptions none of the code > in src in the spkgs is actually checked into the mercurial repos. > There is also no convenient way to figure out which spkgs were used by > sage release x.z.y.
If you ever installed foo-v.spkg, then you can find the version of Sage that it was installed as part of, since it in the corresponding file in spkg/installed. For example: [EMAIL PROTECTED]:~/s/spkg/installed$ more zn_poly-0.8.p0 PACKAGE NAME: zn_poly-0.8.p0 INSTALL DATE: Tue Apr 22 00:22:02 PDT 2008 UNAME: Linux sage 2.6.18-6-amd64 #1 SMP Sun Feb 10 17:50:19 UTC 2008 x86_64 GNU/Linux SAGE VERSION: | SAGE Version 3.0, Release Date: 2008-04-21 Thus you can always tell exactly what version of Sage a given spkg came from, if you installed it. Since we archive all old spkg in sage-x.y.z.tar, storing copies of them in spkg/archive/ is pointless. William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
