Hi 2009/9/5 Mikhail Gusarov <[email protected]>: > > Twas brillig at 11:27:39 05.09.2009 UTC+02 when [email protected] did gyre and > gimble: > > 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"
If I'm not mistaken, the files in /usr/share/Publican are architecture-independent shared libraries, perhaps not libraries in the sense of programming languages like C or Python, but still libraries. > 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. Would you agree that we discuss this with people from Debian Policy and fellow Debian developers on the appropriate mailing lists? I understand that upstream uses an uppercase, but for me it would be preferable to be Debian compliant, and if the wording is unclear, to improve the policy. Best regards -- Danai SAE-HAN (韓達耐) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
