On Thu, Feb 19, 2015 at 11:24 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2015-02-19 16:55, Michael Orlitzky wrote: >> >> It's not incompatibility with Debian that's the problem. Having >> dependencies like "whatever was in the git repo at 11:00 on 2015-02-19 >> UTC-5" leads to madness. > > Why madness? > > It has been done before (#9343) and it worked just fine. > > Waiting forever until PARI makes a new stable release, that's madness. > >> Bundling the git repo is a short-term solution that bones everyone else >> (and possibly us, too, if upstream starts reverting commits) > > If upstream reverts the occasional commit, we can deal with that. Stable > releases also remove/change functionality, so what's the difference? > >> A better >> solution would be to work with them, settle on a set of commits that are >> definitely going to stay, and make a release. Yes, it's more work *right >> now*, but most good ideas are. > > We can't tell PARI to make a new stable release for us, it just doesn't work > that way.
+1 to everything said by anybody who has been the Sage release manager, hence has a better understanding of the constraints. I want to remind people that the goal of Sage is to be a competitor to Mathematica, Matlab, Magma and Maple. This is a very high bar, and it requires doing things that are much harder than what is possible within the framework of constraints of waiting for stable versions of all dependencies to catch up, etc. -- William -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
