[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-haskell-maintainers] libffi soname change upcoming

Hi Matthias,

Am Dienstag, den 23.08.2011, 20:58 +0200 schrieb Matthias Klose:
> as shown in bug #639015, haskell packages make up to 80% of the libffi rdepends,
> which looks a bit insane.  At some time I would like to get the libffi version
> in experimental to unstable, maybe it's worth either waiting until this issue is
> fixed, or coordinate the libffi soname bump or the haskell abi transition (there
> seem to be plenty of it ;)

ok, that explains your motivation :-)

The question that has to be answered first is: Assume the libraries do
not depend on libffi themselves, and only ghc does. Now you update
libffi and ghc gets rebuilds, what will happen:

 A) The haskell ABIs stay the same, the existing library packages can
still be used. Great.

 B) The haskell ABIs change. We’ll have to binNMU all Haskell libraries,
but oh well, not bad thanks to BD-Uninstallable-support in wanna-build
and autosigning.

 C) The haskell ABIs do not change, but the old library builds are
broken nevertheless. Big mess. Hard to recover from, because builds are
not ordered automatically any more. Needs lots of NMUes and Dep-Waits.

Removing the libffi dependencies from the haskell libraries makes C
possible and only helps with A. So until someone investigates this, I’d
rather err on the safe side, leave the dependencies in, and fix the
issue by rebuilding all haskell libraries when you upload the new ffi
soname to unstable.

The next ghc release that is likely to target unstable is expected end
of September.


Joachim "nomeata" Breitner
Debian Developer
  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: