On 2018-06-07 14:36, Timo Kaufmann wrote:
For what its worth, here is debians fix (self-labeled as "extra-hacky") for that issue: https://salsa.debian.org/science-team/sagemath/blob/master/debian/patches/dt-version-glpk-4.60-extra-hacky-fixes.patch
That's not a fix at all. I could easily come up with a doctest that would break using Debian's "fix". So it's certainly not acceptable for Sage.
And I'm not saying there should be absolutely no patches, just that they should be the very last resort.
I mostly agree with this, it's what I'm already doing. It just depends where you put the borderline of "very last resort" and there we probably differ.
But I don't see how this would help distributions. As long as a package has at least 1 essential patch (even a 1-liner in the case of GLPK), distros have to deal with it.
Jeroen. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
