Shibboleth Developers

[Peter Schober <>]

* Cantor, Scott E. 
<>
 [2011-05-20 16:09]:
> So what would be an acceptable location? /usr/local?

Personally I'd prefer not having RPM-managed files in /usr/local at
all, but that's certainly an option (and also the obvious place where
admins would stick it manually).
At least I'd avoid putting it in /usr/local/lib, since then it could
possibly be picked up by other executables more likely by mistake.
(Not that that's expected to do any harm, but better to avoid it.)

I thought maybe /opt/<package> (or /opt/<package>/lib) where <package>
probably is "curl-openssl". The FHS (2.3) also mentions an (optional?)
<provider>/<package> structure in /opt where <provider> is a "LANANA
registered provider" or DNS name, but after getting 403 at lanana.org
and some more chasing this all seems to lead more or less nowhere (in
the vicinity of the LSB specs).

Cf. http://code.google.com/p/chromium/issues/detail?id=24372
(Note that this too ends in a dead link.) As the chrome issue above
would also apply to the Shib IdP maybe it would make sense to use
/opt/shibboleth.net/curl-openssl here (and /opt/shibboleth.net/idp for
the IdP)?
Or just stick it in /usr/local/curl-openssl/lib[64]/libcurl.so
-peter