Shibboleth Developers

["Scott Cantor" <>]

> Also, both the origin and target deployment guides use a default 
> installation directory of `/opt/shibboleth`.  Are there any possible 
> ramifications of installing these on top of each other like this?  
> Perhaps recommend installation directories of 
> `/opt/shibboleth-IdP` and `/opt/shibboleth-SP` or something similar?

It's unusual to install both on the same machine for anything other than
some kind of one-off test or during our development. An origin tends to
always end up in something like /shibboleth-origin-1.2.1 or some such
anyway. Not sure there's any point in even using /opt.

I don't know if they would step on each other, but it's likely they could.

Probably wouldn't hurt to modify the autoconf package for 1.3 to something
other than "shibboleth", though, maybe shibboleth-sp. None of which has
anything to do with where you install it, you can do that however you want.
The RPMs don't use /opt at all. The guides are just lagging reality and
over-simplifying, like docs always do.

Java and C have totally different tools and packaging approaches (Java in
fact has nothing standard when you operate at the level of a software
distribution, it hasn't matured to that point) so trying to create any
coherency out of that is arbitrary.

-- Scott