On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What *standard* Sage spkg packages are out of date right now
> (I'm skimminghttp://sagemath.org/components.html)?
>
> * cddlib: we ship 094b, but 094d is current.
> * clisp: we ship clisp-2.41, but 2.43 is current (I'm sure you can
> comment!)
2.43 is broken on 32 bit Linux x86 with gcc 4.2.x
> * cvxopt: we ship 0.9 but 0.9.1 is out. It has "efficient Python
> classes for dense and sparse matrices (real and complex), with Python
> indexing and slicing and overloaded operations for matrix arithmetic"
> -- looks cool!
> * gd: we ship 2.0.33 but 2.0.36 is current
> * gfan: we ship 0.2.2 but 0.3 is current
Interface issue.
> * givaro: we ship 3.2.6 but 3.2.9 is current
Needs merging back of our patches. Should be done together with the
LinBox update.
> * gmp: we ship 4.2.1 but 4.2.2 is current
[L]GPL issue held that up.
> * gnutls: we ship 1.6.3 but 2.2.0 is current!
[L]GPL issue held that up.
> * gsl: we ship 1.9 but 1.10 is current
[L]GPL issue held that up.
> * jsmath: I don't even know what we ship (it's at most 3.4d), but
> current is 3.4f
> * iml: we ship 1.0.1, but 1.0.2 is current (I think 1.0.2 is
> upstreaming our changes
> in a way that breaks things for us...)
Nope, there remains a 400 line patch outstanding that hasn't been
merged. We should have all the fixes from 1.02 in our 1.01.spkg.
Clement also suggested that we dump IML once the good changes from it
are merged back into LinBox.
> * ipython: we ship 0.8.1, but 0.8.2 is current
> * lcalc: we ship 20070107, but 20070902 is current.
> * libgcrypt: ???
> * Maxima: we ship 5.13, but 5.14 is current.
> * Moinmoin: we ship 1.5.7 but 1.5.8 is current
> * numpy: we ship 1.0.3 but 1.0.4 is current
> * opencdk: we ship 0.5.9 but 0.6.6 is current
> * pari: we ship 2.3.2 but 2.3.3 is current (I posted a new spkg tonight)
> * pexpect: we ship 2.0 but 2.3 is current (2.1 sucked (!); maybe 2.3 is
> good??)
> * lippng: we ship 1.2.22, but 1.2.24 is current
Trouble on older OSX.
> * quaddouble: we ship 2.2, but 2.3.1 is current
> * sqlite: we ship 3.5.3 but 3.5.4 is current
> * sympy: we ship 0.5.7 but 0.5.9 is current
Ondrej will be updating this.
> * zodb: we ship 3.7.0 but 3.7.2 is current
>
> So about half the spkg's in Sage are out of date right now.
"If it ain't broken, don't fix it". Upgrading just for the sake of
upgrading is wrong, but
> What should we do? Any ideas? People who work on Linux distributions,
> please speak up, except for saying "don't bother with Sage, we already
> package everything above in Debian" -- keep in mind Sage also targets OS X
> and Solaris.
And Windows in the future :)
> A possible solution might include:
>
> (1) Find somebody to volunteer for a while to be the "package
> version maiden"
> sort of like how Michael Abshoff has been the "trac maiden".
> This person
> would keep track of a list like the above, possibly only a
> wiki, or possible
> right in trac. For each package, if we aren't upgrading
> there has to be a clear
> reason why.
> (2) Get 2 volunteers to maintain each of the above packages (2
> instead of 1 to
> improve continuity and fill in gaps). Basically
> there are already very hard working package maintainers for
> about half the
> packages in Sage; this list above is the other half.
> (3) Referee spkg updates.
>
> If you're one of the people that lobbied hard for inclusion of a
> package in Sage,
> you might consider volunteering to officially maintain it.
We need to keep a list of spkg and the people involved.
> It's obviously not the end of the world if some of the spkg's in sage aren't
> the
> latest versions -- some projects release new versions very often. But many
> of the projects listed above release a new version maybe once every 6 months,
> so we really need to find a way to get on top of things. That said, there
> are
> often major and difficult integration issues when putting new versions of
> packages in Sage, e.g., updating matplotlib recently caused a lot of pain.
> So we don't want to do things too quickly.
+1
> -- William
>
Cheers,
Michael
> --
> 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
