[Debian-science-sagemath] pari-sage or pari ?

[Jeroen Demeyer]

On 2016-08-21 12:17, Ximin Luo wrote:
> For the purposes of maintaining an OS distribution that satisfies everyone's needs, and not just that of Sage, in the vast majority of cases we do need to stick to release versions. We make exceptions, but these exceptions carry costs and we typically really don't like doing so.
>
> The broader FOSS community understand this principle, and also typically use release-versions of their dependencies. So everyone will depend on version 1.4 of libfoo, instead of having project A depend on libfoo=1.4+425 and project B depend on libfoo=1.4+667 and then this is extra burden on volunteer's time to try to add both to Debian.
>
> This is why it has taken so long to get Sage into Debian. We are constrained by everything else.

I understand the cost for Debian, but consider also the cost for Sage. 
In Sage, we try to use released versions of upstream, but sometimes it's 
easier to use a development or patched version.

Being forced to stick to released versions of packages would be very 
hard for Sage. So we don't plan to do this. PARI is especially bad in 
this regard because they release so slowly. They made a non-bugfix 
release this month, but the one before that was more than 2 years ago! 
We really don't want to wait 2 years to be able to use new PARI features.

I think you should just accept this fact and live with it.

> (BTW, could you fix your mail client to send the proper References: / In-Reply-To: headers, so threading works correctly in standard mail clients?)

It's not my mail client. I only just subscribed to this list, and I am 
copy/pasting from the online archives. From now on (like this email) I 
should do proper replies.