Quoting Sébastien Fabbro <[email protected]>:

On Mon, Jun 24, 2013 at 2:48 PM, Thomas Kahle <[email protected]> wrote:
it is masked.

... and that is irrelavant from a dev perspective.  People report bugs
and we have to come up with solutions.  The mask just makes the problem
less urgent.


we do not have to come up with solutions for glpk api breaks. i could
have simply not bump glpk in the tree and there will be no bugs.
masking or subslot dependencies is what we can do without diving into
upstream code. obviously patches are welcome.

Looking at 4ti2 in particular, that's a substantial amount of code. If you
fix it, that would pretty much get you ownership of it, but I see you already
have a fork on github with a few commits, Thomas.

So you are after glpk documentation on how to migrate? I haven't seen anything
useful on glpk's mailing list but it wouldn't hurt to ask there.

Francois



Reply via email to