Bug#740603: /etc/shibboleth not created when not using libapache2-mod-shib2

[Russ Allbery]

"Cantor, Scott" <cantor.2 at osu.edu> writes:

> They're not linked to, they're plugin extension libraries that are
> specific to the ABI of the surrounding libraries they're built against.

Oh, wait, I missed a subtlety in this, and then failed to make clear what
I had meant by a comment I made earlier.

If the plugins that come with Shibboleth 2.4 (libshibsp5, IIRC) are not
guaranteed to work with Shibboleth 2.5 (libshibsp6), then the way they're
packaged right now only works because they're with the only client that
can currently use them in Debian.  If I break them off into a separate
package, I need to make sure that you either can't get mismatches (the
plugins for libshibsp5 installed but libshibsp6 installed) or that the
plugins are part of the library packages themselves.  The latter would be
my preference, but the current problem with *that* is that the plugins are
in /usr/lib/$arch/shibboleth directly.  If I put that into the library
packages, that means libshibsp5 and libshibsp6 can't be installed
simultaneously, which Debian requires so that it's possible to upgrade
shared libraries without undue pain.

In other words, if they're linked to particular library SONAMEs, they
should be in a directory that changes with the library SONAME, such as
/usr/lib/$arch/shibboleth/5/ and /6/.

Does that make sense?  And if so, would it be easy for me to move the
plugins to such a directory in some way?  I'd need to make sure that the
library knew where to load them from, of course.  It's not immediately
obvious to me how, although I'm guessing it's related to SHIBSP_LIBDIR.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>