On Nov 27, 8:25 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 27, 2008 at 1:34 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > let's forget 3.2.1.alpha1 ever happened :)
>
> > 3.2.1.alpha2 fixes the build issues from its predecessor (I did a full
> > build cycle before announcing here, so no need to do an alpha3 in the
> > next 24 hours) and adds a couple additional patches. One very
> > interesting patch set is #463 by William which will allow
>
> > ./sage -upgrade foo.org/home/bar/sage-3.4.5.alpha2
>
> > in the future, i.e. you can upgrade to any install either via
> > webserver or even by directory on a local disk.
>
> (pulling from a local disk isn't implemented yet)
My bad, I clearly needed sleep when I wrote the release notes. :)
> > But nothing like that
> > is bug free and since the infrastructure to do the in place upgrade to
> > other versions isn't in anything but 3.2.1.alpha2 yet the upgrade is
>
> You can try it out with any 3.2.1.*alpha* build in pretty much any broken
> or whatever state. Since you're probably going to throw away such builds
> anyways, why not try this out. Just do:
>
> ./sage
> -ihttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sa...
>
> ./sage
> -upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sa...
>
> The first line installs the upgraded scripts spkg, which has the new
> upgrade command. The second line upgrades from Michael's tree. Note
> that this may be surprisingly fast, since we no longer do "sage -ba"
> to upgrade the core library.
Note that if you do the above you need to have a Sage with IPython
0.8.4 installed since the scripts repo contains fixes that are
dependent on its presence. Other than that give it a try and let us
know if/how it blows up. Future releases will not have that problem
since -upgrade would install all of those dependencies before the
scripts repo. It will be very cool and convenient to have once the
bugs are ironed out.
I plan to put the files required for upgrades alongside the tarball,
ie.
./sage -upgrade
http://sage.math.washington.edu/home/mabshoff/release-cycles-x.y.z/sage-x.yz.[alphaX|rcX|final]
should be the canonical place to upgrade from for "my" dev version
sage-x.yz.[alphaX|rcX|final]. Due to space constraints I will likely
delete those directories when x.y.z is released just like I now delete
source and binary tarballs.
> On the other hand it might just not work at all -- this is a totally new
> feature
> and it definitely has problems:
Yep.
Cheers,
Michael
<SNIP>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
