On 2016-03-11 12:03, Erik Bray wrote:
But really (especially these days) that should be a minority case, and Sage should have just used the `patch` I have.
Since recently, I started adding some general mechanism to actually do this. I.e. make the special case that we currently have for GCC the general case. So, be patient and it will happen.
We still need to think about how we determine whether the system version of a package is good enough. For GCC, this is actually about 200 lines in configure.ac.
For executables, we could probably just look at the output of "PROGRAM --version" but then we need to decide which versions are good: for example, does GNU patch 2.6.1 work with Sage?
In general, this is not an easy problem... 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.
