Comment #9 on issue 3539 by [email protected]: Configure should
forbid mpost 1.802 from TexLive 2013
http://code.google.com/p/lilypond/issues/detail?id=3539
Here is Taco's answer:
About question 3: the bug was introduced in the big rewrite that started
after the 1.5xx series. The first released version that used the new code
was 1.770, but the rewrite started at (internal) version number 1.600. It
was fixed for version 1.803. Since the Metapost repository is always open
for reading, it makes sense to block everything from 1.600 upto 1.802,
inclusive.
MetaPost version numbers are <major>.<minor>, where <minor> is always three
digits.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings