Bug#700759: Shared library policy on private libs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/19/2013 08:30 PM, Sam Hartman wrote:
> Uh, no. If you don't install a .so, then linking with -lfoo won't
> work.
I assumed you meant to just leave the .so in the app package, not a
separate -dev package. Obviously there not being a .so in the first
place makes this whole discussion moot.
> In general though I think including no headers and no .so for a
> library makes a clear statement that build systems tend to
> respect:-)
Not having the .pc file and headers etc in the -dev package would
prevent the build of anything with a decent pkg-config enabled build
system, so that could work with a tweak to the policy to allow it.
That would prevent the building of broken packages, though it's a bit
of throwing the baby out with the bath water. It would be preferable
to allow the build, but with a warning and a strict == dependency
instead of the >= one.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJRJFNCAAoJEJrBOlT6nu75v8AIANLXbnsiU67N196IjH2dxwf2
AxkIBMYx11MVs9SaHdGXPG30s5KxPP6EvJb3SNdzUiwBQ828aDoCLBuctHZ6uFXw
Iuy4qKtwh5rbifjEqyJL+gdPGkyvlQiO4RgS8VEb4K4G/0kKFFHN5/khpnrUEk3+
MjVzxfdDiMVws1RG032UsgYqS+Ga2QCQHcUSQ5QEt51olZIjpMKZ/iSI7UCWMzbB
kvt6Rlo/6tC0rtXhSBoQb8KCnjNadECdwWaDK2eQzOAE5CYgFYTSdqnXxDNDp1IN
5iIB3RS0ra0GGo/6mSxLti+BiPsPjHTz3JW/0FH+7pOvyMy9hp+7ld6z/gWBEKM=
=xww2
-----END PGP SIGNATURE-----
Reply to: