On Tue, Aug 17, 2010 at 05:16:09PM +0200, Reinhard Tartler wrote:
On Tue, Aug 17, 2010 at 15:35:10 (CEST), Hans-Christoph Steiner wrote:README.txt and LICENSE.txt are part of the Pd library format. They are part of the library, and the Help Browser (aka the library browser) looks for them to display them. The library format is basically a directory with files in it, and a subdir called 'examples'. That install target actually serves to enforce that all the standard files are there.In this library, I could replace the file with a symlink to ../../../ common-licenses/GPL-2, but other libraries might have different licenses so this wouldn't always be the case.I guess that both the license and the README.txt actually belongs to /usr/share/doc/$package, that's what debian policy tells us to do. IIRC, documentation browsers like dhelp and the default webserver's configurations publish /usr/share/doc so that users can browse package documentation.So moving these files and symlink them to where the package expect them seems to me the right thing to do.
This is wrong, actually:Code must not depend on /usr/share/doc existing on the machine, so when a file is needed both by runtime and below /usr/share/doc then the actual file should be placed elsewhere and a symlink be placed below /usr/share/doc.
Not sure if this is explicitly clarified in Debian Policy or only a result of close-reading FHS (File Hierarchy Standard) or some such. Perhaps look for sections regarding example scripts.
- Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Description: Digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list firstname.lastname@example.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers