Twas brillig at 11:27:39 05.09.2009 UTC+02 when [email protected] did gyre and gimble:
DS> preferably under /usr/share/package-name. Following the DS> package-name naming convention ensures that the file names change DS> when the shared object version changes. Not applicable, no shared packages. DS> Under 10.7.3: A common practice is to create a script called DS> package-configure and have the package's postinst call it if and DS> only if the configuration file does not already exist. In certain DS> cases it is useful for there to be an example or template file DS> which the maintainer scripts use. Such files should be in DS> /usr/share/package or /usr/lib/package (depending on whether they DS> are architecture-independent or not). Not applicable, no publican-configure. Actually wording here is unclear, it will make much more sense if spelled like "such files should be in directory where package stores it's own arch-indep or arch-dep files" >> DS> Every package here is in lowercase. >> /usr/share/X11 DS> There are exceptions such as X11 and R. But let's not make things DS> too difficult: (almost) every package is in lowercase. It is no DS> help that end users should start looking if the name is in upper or DS> lowercase. /usr/share/BasiliskII /usr/share/PolicyKit /usr/share/VFlib /usr/share/Thunar /usr/share/ImageMagick-<ver> /usr/share/FBReader /usr/share/DVIlib2 and /usr/lib/ConsoleKit /usr/lib/X11 /usr/lib/ImageMagick-<ver> You might want to try to persuade upstream to use /usr/share/publican, I'm not going to change it just for sake of complying with recomendations for shared libraries, which aren't applicable in this particular case. -- http://fossarchy.blogspot.com/
pgpWHrY3qrsSh.pgp
Description: PGP signature
