Re: Forge packages recompiled against Octave 5 no longer depend on liboctave7
* Mike Miller <mtmiller@debian.org> [2019-10-25 16:58]:
For reference, the mechanism that Octave uses is to compile the text
value of OCTAVE_API_VERSION into each oct file, and compare it against
Octave's own value at run time. If I build an oct file with Octave
4.4.1, the string "api-v52" is compiled in. If Octave 5.1.0 tries to
load that oct file, it fails to compare with the new value of "api-v53"
and reports an error.
The upstream Octave release process always increments this string before
every major release. I think we still plan to release Octave 6.1.0 early
next year, and it should provide "api-v54". It's possible that the
release candidates may contain the string "api-v53+". But again, I think
it's probably prudent for octave-abi-N to use an independent number
scheme, just in case we make a mistake upstream or something changes
again.
Thank you for this detailed explanation, Mike!
i think I will go ahead and release the version of dh-octave that
implements the octave-abi-N dependency. Just a further question: should I
make the N in octave-abi-N the same as the N in liboctaveN?
Best,
Rafael
Reply to: