Coordinating libffi upgrade

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Fri, 02 Nov 2012 16:04:29 -0400
Adam Jackson <ajax at redhat.com> escribió:
> On 11/2/12 3:18 PM, Anthony Green wrote:
> > Several months ago I attempted to upgrade libffi 3.0.10 to 3.0.11.
> > The change was reverted because the soname change in this version of
> > the library broke the build environment.  I would still like to get
> > 3.0.11 in Fedora.  I don't anticipate any future ABI-breaking
> > changes, and 3.0.12 will include additional ports like Aarch64,
> > which is likely of interest to some Fedora developers.  How do we
> > coordinate a rebuild for dependent packages?  Also, I assume this
> > will have to wait 'til F18 is out (fine by me), but I'd like to deal
> > with it early in the F19 cycle.
> 
> It looks like libffi is emitted into the minimal buildroot (rpm-build
> -> pkg-config -> glib2 -> libffi), so during the transition we'll
> need to build both sonames of libffi.  It might be worth keeping a
> compat-libffi around for a release or two anyway, the current soname
> has a _long_ history.

I am right now building a compat-libffi package that has just the
old .so nothing to be built against. so expect that early this week
the .so of libffi will be bumped.

Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlD0TvoACgkQkSxm47BaWfeWkwCeN3gJR5lfWjgPwWYjpFeN/KTl
5/8AoJ4JaVMRJct2RsSG57QVHHk5flET
=WBEh
-----END PGP SIGNATURE-----