On 23/10/13 18:12, David Kastrup wrote:
Should we create a release of 2.16.3 which only differs from 2.16.2 in
cherry-picking the autoconf change making it refuse to compile with
buggy versions of Metapost?
Well personally I think we should 'warn' than refuse to compile. Those
that know how to 'go back' to an earlier version of metapost will, those
that don't will not then be stuck with something that doesn't work.
If you see what I mean.
James
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel