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

[Russ Allbery]

<stefan.paetow at diamond.ac.uk> writes:

> The libapache2-mod-shib2 package contains the files for
> /etc/shibboleth. When you do not use libapache2-mod-shib (as we do in
> the Moonshot project), the contents for that directory does not get
> installed. The file listing for the package confirms this:
> https://packages.debian.org/squeeze/amd64/libapache2-mod-shib2/filelist

> While in the RHEL distributions the Shibboleth SP is completely
> self-contained, i.e. it installs the Apache module as well as the Shibd
> binary and all the schemas, Debian has increased the granularity and
> makes the schemas available separately. Shouldn't the /etc/shibboleth
> files be either in a separate package, or be moved to the package that
> actually requires them (libshibsp5 for example does require them, and
> libapache2-mod-shib2 requires libshibsp5, as seen as part of this in the
> Moonshot project).

Could you explain a bit more about what the use case is?  I think I
understand, but I'm not sure.  You're using libshibsp5, and you want the
standard configuration files, but you aren't using Apache so you don't
want libapache2-mod-shib2?  (Or, I guess, to be more precise, you don't
want the apache2-api-20120211 dependency, since the extra files in
libapache2-mod-shib2 are harmless.)

Do you want shibd?

The configuration files obviously can't go into libshibsp5 (see Debian
Policy 8.2), so I need to understand the use case better to figure out how
to properly split the packages up.  I know that shibd can be run on a
separate host from the Apache module, but this isn't currently supported
by the package breakdown.  Maybe this is a similar sort of case?

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