Hi 2009/9/5 Mikhail Gusarov <[email protected]>: > > Twas brillig at 10:20:31 05.09.2009 UTC+02 when [email protected] did > gyre and gimble: > > DS> Please put everything in /usr/share/publican, not > DS> /usr/share/Publican. > > Is it dictated by Policy? Upstream uses /usr/share/Publican and I'm > reluctant to change it unless there are serious objections.
Not required, but certainly recommended. The Policy says under 8.2: It is recommended that supporting files and run-time support programs that do not need to be invoked manually by users, but are nevertheless required for the package to function, be placed (if they are binary) in a subdirectory of /usr/lib, preferably under /usr/lib/package-name. If the program or file is architecture independent, the recommendation is for it to be placed in a subdirectory of /usr/share instead, preferably under /usr/share/package-name. Following the package-name naming convention ensures that the file names change when the shared object version changes. Under 10.7.3: A common practice is to create a script called package-configure and have the package's postinst call it if and only if the configuration file does not already exist. In certain cases it is useful for there to be an example or template file which the maintainer scripts use. Such files should be in /usr/share/package or /usr/lib/package (depending on whether they are architecture-independent or not). There should be symbolic links to them from /usr/share/doc/package/examples if they are examples, and should be perfectly ordinary dpkg-handled files (not configuration files). Given that $package is `publican' in this case, I would put it in lowercase. > DS> Every package here is in lowercase. > > /usr/share/X11 There are exceptions such as X11 and R. But let's not make things too difficult: (almost) every package is in lowercase. It is no help that end users should start looking if the name is in upper or lowercase. Best regards -- Danai SAE-HAN (韓達耐) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
