On Mar 24, 2012, at 13:20 , Starx wrote: > Ok, so if -upgrade only works for upgrading a stable release, to > upgrade from one beta to a newer beta you just build from the source > and manually transfer mercurial patches?
I believe that's doomed to failure (often, in subtle ways). As mentioned previously, Jeroen's method is to start a new development release from the previous stable release and then add a mysterious mixture of new patches. The sets of patches of the various devel releases are not guaranteed to have any fixed relation among themselves, so just "adding more" to the mix doesn't always work. In particular, the patches for a specific trac item may be modified between one development release and the next. I always do this, when I upgrade, by first duping the previous stable tree, and then upgrading that. There may be a few mercurial glitches when you start the upgrade, but in my experience, they are easily dealt with. HTH Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income -------- When LuteFisk is outlawed, Only outlaws will have LuteFisk -------- -- 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
