Shibboleth2 packaging

[Scott Cantor]

To answer some of your questions:

I seriously doubt there is any way to package both SP versions at once.
Everything from opensaml up is specific to each version and there is no
compatibility, as I think you realized.

While you can certainly install both library sets, you CANNOT install both
SPs anyway, so there's no basis for supporting both libraries at this point.
OpenSAML never attracted any serious non-Shib use, intentionally, so there's
no compelling reason to maintain 1.x as a library if you ship the 2.0 SP.

I made a conscious choice NOT to rename the opensaml package to opensaml2.
If I had, it would have facilitated side by side installs of the headers. I
did not want that to be a simple thing for people to do because I don't want
to support that code long term, so I made it harder for that to happen.

A couple of other questions...

The schemas are absolutely required by Shibboleth. They're mandatory for 1.3
which validates everything. 2.0 is less strict, but they're still needed.

There is no reason to package the -lite libraries separately as they will
NEVER be versioned separately from the non-lite version of the same library.
The libtool version will change for both when it does change. There are only
a few library pairs, and only two are versioned (xmltooling and shibsp).

-- Scott