| Summary: | samba swat; why on /usr/share/doc? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Norberto Bensa <nbensa> |
| Component: | [OLD] Server | Assignee: | Gentoo's SAMBA Team <samba> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Norberto Bensa
2005-06-13 20:45:07 UTC
You're right, but unfortunately the (samba upstream) install phase does consider swat and the documentation a unique subpackage. So, not only swat includes documentation, but it has statical references to it also. Until a patch to the install Makefile is submitted (and maintained), I'd prefer not to change this behaviour. I'm sorry, but I fail to see what's wrong with:
--with-swatdir=/usr/$(get_libdir)/samba/swat \
in the ebuild.
Why do we need a patch for the Makefile?
I see the statical references to the documentation in swat as help files for
the application. So shouldn't them be installed together?
Do you want to separate this documentation/help from swat?
Thanks,
Norberto
well, although installed as part of swat, the documentation should respect both FSH and Gentoo standards: they state that documentation goes under /usr/share/doc/<package> or /usr/doc/<package>, while /usr/lib/<whatever> should be for non-doc components. So the location of swat is now bound to the location of docs. If swat would be separated, I will be happy to put it in a 'more proper' :-) site. |
