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

Cantor, Scott cantor.2 at osu.edu
Mon Mar 17 02:39:38 UTC 2014


On 3/16/14, 10:31 PM, "Russ Allbery" <rra at debian.org> wrote:
>
>Hm, okay, in that case I'm inclined to change the -common package to
>-runtime (which is a more typical convention for arch-dependent supporting
>files for libraries), put both the configuration and the plugins in that,
>and have the library package depend on it.  Does that make sense?

Yes, probably so. I would say runtime is a pretty good description. But is
it acceptable to have the library package depend on this when there are
files in it that in turn are linked to the libraries? That seems circular.

>Yeah, so having the library package depend on them needlessly pulls in
>those shared libraries.  But I'm not sure further splitting is worth it to
>avoid a few dependencies.  Debian tends to generate a lot of dependencies
>on shared libraries and not worry about that too much.

That's fine, just noting it.

>I kind of hate to add three more packages, but I think those all make
>coherent sense, and in the long run its only an addition of two packages.
>And that resolves the FastCGI program problem as well.

That looks good to me.

-- Scott



More information about the Pkg-shibboleth-devel mailing list