Le 18/02/2015 17:59, Bruno Grenet a écrit :
Le 18/02/2015 17:44, Jeroen Demeyer a écrit :
On 2015-02-18 17:22, Vincent Delecroix wrote:
Julien built an almost working prototype for a native sage on debian.
This implies out of the box installation for a lot of users (and
potentially much cleaner integration of third party softwares). The
real question is:
does the Sage community will officially support sage on debian ?
Sage shouldn't support Debian. Debian should support Sage.
Agreed. That's what debian maintainers do:
- they collect bug reports from users, and filter them before forwarding
to upstream, sometimes with a nice ready-to-apply fix ;
- they also get reports from the debian package-building tools, which
detect problems within the software, and also filter the false positives
before forwarding to upstream, possibly with a fix.
Ask around : getting packaged in debian is not a problem.
Sage already works on Debian, just build from source. Debian could
easily make a Sage package if they wanted. However, Debian doesn't
like the "batteries included" of Sage. Fine, but that's Debian's
problem and not Sage's problem.
I don't think the discussing about who's fault it is will bring us
anywhere. It would be nice for both Debian and Sage to have Sage
included in Debian.The point is that a Debian package is not suppose to
come with its dependencies included, but is supposed to depend on its
dependencies. That's a matter of fact, and we should deal with this.
Yes. Sage-the-software should say it depends on foo 3.14, bar 2.57, etc.
Then its package will also depend on those.
Imagine that Sage officially support Debian. Now Sage wants to upgrade
some package to a version that Debian doesn't ship. Then what?
Requiring such support would only slow down Sage development further.
In many softwares, you have in Debian repositories a version which is
slightly older than the version you can get by building from the source.
I don't see this as a problem. As soon as a stable version of Sage does
not depend on an unstable version of some package, it should not pause
any problem.
If Debian doesn't ship the latest stable version of package X, and Sage
needs this latest version, a ticket is opened on Debian side to upgrade
package X. It doesn't slows Sage development (that is done using the
development version, built from sources), simply slows a bit the upgrade
of Sage to its latest stable version in Debian!
The above paragraph is right on spot.
Snark on #sagemath
--
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.
