I've heard that sage 3.4 was going to be something of an LTS, a "stable" release. If so, it would be brilliant to include this one with ubuntu, and then not produce another ubuntu package before the next LTS. The custom with such repositories, even more so with debian, is certainly not to get the latest version at all cost (which has been pointed out already a couple of times on this list).
pierre On 6 mar, 05:27, Ben Goodrich <goodrich....@gmail.com> wrote: > On Mar 5, 11:27 pm, "Dr. David Kirkby" <david.kir...@onetel.net> > wrote: > > > I suspect the Debian people are reasonable and could be persuaded to accept > > things if there were aware of just how many patches have needed to be made > > to > > 'standard' packages. > > They are reasonable. My guess is they would usually email upstream to > ask about a patch and if upstream agrees but isn't planning to release > for a while, then the maintainers might well apply it, particularly in > experimental. But all that would take time and may have to be > coordinated across several package maintainers. That is why I agree > with you about having an option to build sage with reasonably up-to- > date versions of system libraries and dependencies. I think that would > probably be the biggest thing that could be done to make life easier > on Tim and the other package maintainers. > > Also, with Debian in particular, when they freeze the testing branch > to start preparing it for the stable release, there is going to be > extra reluctance to take new patches, often even for the unstable > branch. The maintainers just devote all their energy toward > stabilizing and other things get backlogged. Being Debian, freezes > have been known to last a long time. > > Ben -- 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
