review request for libpst

[Carl Byington]

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

Thanks to everyone for their comments. Thinking about this dependency
from the main libpst package to the -libs subpackage, it seems that we
should have

Requires: %{name}-libs >= %{version}-%{release}

in the main package. Currently, the soname is libpst.so.2 with libtool
- -version-info 2:0:0 and library name libpst.so.2.0.0. If we add some
interfaces, but don't change any existing interfaces, then
- -version-info goes to 3:0:1 and the soname stays at libpst.so.2 and
the
library name is libpst.so.2.1.0. We need some mechanism to capture that
dependency. Yes, this version of the executables needs libpst.so.2, but
it won't run with the original libpst.so.2.0.0. How is this sort of
dependency handled in other packages? I think the above Requires solves
that within this package.

It would also be nice to allow installing multiple (matching) -devel
and -libs packages for different major versions.

<http://www106.pair.com/rhp/parallel.html>

Is there anything (else) that needs to be done to enable parallel
installs for this package? The -devel include files already go into
/usr/include/libpst-2 where the 2 comes from the SONAME. 

If we change interfaces, with -version-info up to 4:0:0, soname is
libpst.so.4, library name is libpst.so.4.0.0, and the headers go into
/usr/include/libpst-4. Is there anything here that would prevent
parallel installs for the so.2 and so.4 versions?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFJ3ipSL6j7milTFsERAjGvAJ4nmjSFua2i6qUuMQw2Wb1vywtF3gCgh+zh
+tChxi3mgakAlmELC7dN2FQ=
=+Og2
-----END PGP SIGNATURE-----