Re: GLPK API change

[John W. Eaton]

On  8-Feb-2007, Rafael Laboissiere wrote:

| * address@hidden <address@hidden> [2007-02-08 14:44]:
| 
| > I wanted to update the GLPK library to the latest version (4.14), but it
| > appears that the API has changed, leading to compilation errors in
| > __glpk__.cc. See the following (ugly) patch to see what changes are
| > required.
| > 
| > The previous version I was using is 4.9. So the question is: should octave
| > require the latest version of GLPK (and __glpk__.cc should be changed
| > accordingly, not with my ugly patch), or should it support both API?
| 
| I would vote for requiring the latest version of GLPK.  Supporting
| incompatible versions of libraries is usually a pain.

OK, but what is the right feature test for autoconf in this case?  We
should not be encoding version numbers there if at all possible.

jwe