Shibboleth Developers

["Cantor, Scott E." <>]

On 5/20/11 11:37 AM, "Peter Schober" 
<>
 wrote:
>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).

That's encouraging.

>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

I do favor using curl-openssl as the prefix, whatever I do, as this isn't
SP code or really anything to do with it.

I don't think it matters too much how this works for Debian or Ubuntu,
which seems to treat packaging and file locations as something more
important than religion, since they have their own curl-openssl packaging
already.

But I'd like to get more feedback on using /opt/shibboleth.net

-- Scott