Re: Forge packages recompiled against Octave 5 no longer depend on liboctave7
* Sébastien Villemot <sebastien@debian.org> [2019-10-04 10:12]:
I don’t think injecting an artificial liboctaveN dependency is a very
good solution, because it violates the usual assumptions about
dependencies on shared libraries, and it goes against upstream’s will
to eliminate this dependency.
Nevertheless, I think we’ll have to design something along similar
lines. Either adding versioned dependencies against Octave as Mike
suggested, or introducing a virtual ABI package as is for example done
for R.
Yes, injecting an artificial liboctaveN dependency is not a perfect
solution. However, my code can be easily modified to inject the virtual
package octave-abi-N instead of liboctaveN. The octave package must be
changed such that the liboctaveN package provides octave-abi-N. What do
you think?
However, may I suggest that we postpone that work for later, and that
for the time being we focus on completing the Octave 5 transition?
Other transitions are waiting for ours to complete, and there are about
16 packages (inside and outside the DOG) currently failing to compile
against Octave 5.
Yes, let us postpone this work for when the Octave 5 transition is
completed. I will try to look at some of current build failures.
Rafeal
Reply to: