Shibboleth Developers

["Cantor, Scott E." <>]

> Indeed all those *.txt files should probably go into %{_docdir}/%{name}/
> possibly dropping INSTALL.txt from the RPM entirely (or replacing it
> with some other content, see below).

I know where they should go formally, but as I said earlier, if we do that, 
people won't see them, so there's no point in including them at all. I think 
the best option, if they matter, is to leave them be.

I don't think there's any way to package this with any normal conventions and 
end up with something useful.
 
> The file shibboleth-ds.conf seemingly is an Apache httpd config
> snippet and would go into %{_sysconfdir}/(httpd|apache2)/conf.d
> (I suppose this is planned, same as for the shib SP package).

Yes, it is installed there.
 
> As for the rest I first thought /var/ seems to be right (it's for
> "variable data files", after all), but none of the required
> subdirectories seem to fit (I was originally thinking /var/lib/%{name}
> but the FHS explicitly says "Users must never need to modify files in
> /var/lib to configure a package's operation.") and packages are
> usually not welcome to add their own directories to /var (as in
> /var/%{name}).

I think var is for runtime state, but not for content that is "stable", so 
these don't fit.

> /usr/share/ also won't help (/usr might be mounted read-only), which
> would otherwise be common for HTML and JS files.

Correct.

> So at least some part of the lack of (my) feedback comes from a lack
> of ideas improving upon "stick it all in /etc".

I think that's the only compromise. There simply isn't any support for 
editable web content in the file system layout.

> Btw, INSTALL.txt contains a link to:
> https://wiki.shibboleth.net/confluence/display/EDS10/Installation+and+Con
> figuration+Guide
> which currently does not exist (page renaming?)

Can you file a bug? I don't want to get too deep into actually fixing the 
software itself.

> There probably needs to be an RPM-specific "install" document, because
> the upstream docs won't help here (you'd be downloading the eds
> package again, manually putting files in your local filesystem, etc.).
> In "Web Page Setup" the script/@source would point to the aliased
> values from shibboleth-ds.conf, etc.

Yes. I don't think we're releasing this until the docs are ready.

-- Scott