[Pkg-octave-devel] Re: Forking glpk

John W. Eaton jwe at bevo.che.wisc.edu
Wed Nov 16 00:27:13 UTC 2005


On 15-Nov-2005, Falk Hueffner wrote:

| The difference is that the *ABI* changes frequently.

I think that happens for a lot of software.

| This will break horribly if the headers become out of sync with the
| library. You absolutely need to provide matching headers.

Yes, of course.  So maybe a different solution is needed?

| I'm not really convinced. The problem is that you'll need a new
| package name each time you upgrade, and this will leave lots of stale
| library packages behind and generally be a hassle.

Why is it a hassle?  How often are new releases of glpk happening?
Every few weeks?  Twice a year?  Does the ABI change with every
release?

| If the goal is only
| to provide a solution for octave, it would probably be easier to just
| add a copy of glpk's source into the octave tarball and install it as
| glpk-octave or something.

No.  I do not want to include external packages in Octave.  Doing that
would definitely be a hassle.

jwe



More information about the Pkg-octave-devel mailing list