how to handle a gui- and non-gui-version of the same library/soname

[Stephen Gallagher]

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

On 01/17/2010 09:04 AM, Milos Jakubicek wrote:
> Hi all,
> 
> is there any good way how to handle the situation described at
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=528524
> 
> ?
> 
> I.e. you have a single library (single soname) which can be compiled 
> with or without GUI support (with different ABI) -- and we'd like to 
> have both of them, of course -- the non-GUI version on headless servers, 
> the GUI one for desktop.
> 
> As far "yelling at upstream" sounds like the most correct way.
> 
> Thanks in advance for any advice,
> Milos

This is not a properly-built library. You can't have the same SONAME and
different ABI. That's the entire point of a SONAME. The proper way would
be to build the library always with GUI support and then not USE the GUI
portions of the ABI unless you need to.

If they also have different API, I strongly recommend yelling at upstream.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAktUUUYACgkQeiVVYja6o6MZMwCfZuVWm6b/KUZt+kFM8UZvDnEa
bkgAoJdVOilpn5Wr+H+iX0yh8QJvuqhf
=9wvy
-----END PGP SIGNATURE-----