Shibboleth2 packaging

[Scott Cantor]

> Ah, okay.  I feel better now; we're more on the same page than I thought.
> Yeah, I don't think we should go to any effort to make them co-installable
> given that, but it may be good to hang on to separate, conflicting
> packages for both versions for one release cycle, particularly since it's
> so late for lenny.

Yes, I agree.

> Basically, the only reason to package them separately is if libshib might
> change SONAMEs when libshib-target didn't, or vice versa.  If whenever one
> of them changes, the other one is *guaranteed* to change, then they can go
> into a single library package.  Otherwise, it's better to split them since
> then dependencies will always be right.

In practice, there's no likely application that would ever link to one and
not the other (which is one reason there's no libshib anymore, just
libshibsp), but formally you're right.

-- Scott