On Thu, Sep 01, 2016 at 09:29:28PM +0100, Jerome BENOIT wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi, thanks for your reply.
> 
> On 01/09/16 20:29, Bill Allombert wrote:
> > On Sun, Aug 21, 2016 at 02:37:11PM +0100, Jerome Benoit wrote:
> >> Source: pari
> >> Severity: wishlist
> >>
> >> Dear Maintainer,
> >>
> >>    it appears that the current sage[math] (version 7.3) cannot build 
> >> against PARI 2.7,
> >>    while is might against PARI 2.8.0.alpha .
> > 
> > As far as I understand SAGE use some unspecified GIT snapshot of PARI
> > and not an official release.
> 
> There was a (long) discussion on the Debain Sage list about this
> mater, and it almost end up here.
> The latest stable version of Sage builds against PARI 2.8.0[.alpha]
> and the consensus among the Debian Sage Team is to stick to Sage
> version depending on official version of PARI. The point was made
> clear
> along the discussion. In short, we do not plan to use some unspecified
> GIT snapshot of PARI, but PARI 2.8.
> Can you package the version 2.8.0.alpha in experimental ? If you do
> not have time, I would be glad to
> open such an experimental branch. This will certainly save some energy.

I discussed with upstream and having PARI 2.8.0 in experimental 
is a bad idea. It is better to wait for PARI 2.9.0 to be released.

PARI 2.8.1 will be released in about one month and will be API/ABI
incompatible with 2.8.0. Then PARI 2.9.0 will be released.
We should focus on PARI 2.9.0 and not be distracted with 2.8.0.

Making valid Debian packages for PARI 2.8.0 is difficult, even in
experimental.
First the PARI library is not versionned the same way in stable and
unstable release, so the packaging need to be adjusted to take that into
account (something pari-sage does not do).
Secondly, such experimental packages must not interfer with the packages
for PARI 2.7.6, so different package names and filepath needs to be
used. pari-sage does not do that either.

And then you have to change Sage to use the new names and new paths.

You should just bundle pari 2.8.0 in the Sage tarball in the meantime. This
would be far less disruptive. Then when PARI 2.9.0 is released, you can
move to that.

Cheers,
-- 
Bill. <ballo...@debian.org>

Imagine a large red swirl here. 

Reply via email to