Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Package: publican Version: 1.0~20090927-1 Severity: minor Hi Please put everything in /usr/share/publican, not /usr/share/Publican. Every package here is in lowercase. Cheerio -- Danai SAE-HAN (韓達耐) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/1 CPU core) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages publican depends on: ii docbook-xml4.5-6 standard XML documentation system, ii docbook-xsl1.75.2+dfsg-2 stylesheets for processing DocBook ii fop1:0.95.dfsg-5 XML to PDF Translator ii gettext0.17-8GNU Internationalization utilities ii libbatik-java 1.7-4 xml.apache.org SVG Library ii libclass-trigger-perl 0.13-1Mix-in to add / call inheritable t ii libclone-perl 0.31-1recursively copy Perl datatypes ii libconfig-simple-perl 4.59-3simple configuration file class ii libdatetime-format-datepar 0.04-1Perl module parsing Date::Parse co ii libdatetime-perl 2:0.4900-1perl DateTime - Reference implemen ii libfile-copy-recursive-per 0.38-1Perl extension for recursively cop ii libfile-find-rule-perl 0.30-3Alternative interface to File::Fin ii libfile-slurp-perl .12-2 single call read write file rout ii libhtml-format-perl2.04-2format HTML syntax trees into text ii libhtml-tree-perl 3.23-1represent and create HTML syntax t ii libimage-size-perl 3.2-3 Perl module for determining images ii liblocale-maketext-gettext 1.28-1Perl module bridging gettext and M ii liblocale-po-perl 0.21-1Locale::PO perl module ii libmakefile-dom-perl 0.004-1 Perl DOM implementation for Makefi ii libmakefile-parser-perl0.211-1 simple Perl Makefile parser ii libparams-util-perl0.38-2Perl extension for simple standalo ii libsyntax-highlight-engine 0.05+dfsg-1 port to Perl of the syntax highlig ii libxml-libxml-perl 1.69.ds-2 Perl module for using the GNOME li ii libxml-libxslt-perl1.68-2Perl module for using the GNOME li ii libxml-treebuilder-perl3.09-1XML parser providing XML::Elements ii perl 5.10.0-25 Larry Wall's Practical Extraction ii perlmagick 7:6.5.5.3-1 Perl interface to the ImageMagick publican recommends no packages. publican suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
tags 545127 wontfix stop Twas brillig at 10:20:31 05.09.2009 UTC+02 when da...@debian.org 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. DS Every package here is in lowercase. /usr/share/X11 -- http://fossarchy.blogspot.com/ pgpY0BeP3IxFc.pgp Description: PGP signature
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Hi 2009/9/5 Mikhail Gusarov dotted...@dottedmag.net: Twas brillig at 10:20:31 05.09.2009 UTC+02 when da...@debian.org 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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Twas brillig at 11:27:39 05.09.2009 UTC+02 when da...@debian.org 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
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Hi 2009/9/5 Mikhail Gusarov dotted...@dottedmag.net: Twas brillig at 11:27:39 05.09.2009 UTC+02 when da...@debian.org 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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Ok, will do. Changing /usr/share/PolicyKit - /usr/share/policykit will be beneficial in particular. Everyone will be happy changing upstream's policies installation path. I don't understand what upstream's policies have anything to do here. As long as Debian's is respected. =) Nothing upstream should be changed. Perhaps notified that on Debian + derivatives it is different, but that is totally up to the maintainer to decide, IMHO. Best regards -- Danai SAE-HAN (韓達耐) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Twas brillig at 12:25:53 05.09.2009 UTC+02 when da...@debian.org did gyre and
gimble:
Changing /usr/share/PolicyKit - /usr/share/policykit will be
beneficial in particular. Everyone will be happy changing upstream's
policies installation path.
DS I don't understand what upstream's policies have anything to do
DS here.
Various packages ship policies for PolicyKit, and they all assume such
policies go to $prefix/share/PolicyKit. If you insist on
lowercasification of /usr/share contents (and I won't touch the code
until all maintainers for all packages with uppercase directories in
/usr/{lib,share} agree to lowercase directories of their packages), then
every maintainer of package which contains policy for PolicyKit will
have to adjust.
--
http://fossarchy.blogspot.com/
pgpeG0v9hjBxh.pgp
Description: PGP signature
Bug#545127: Put everything in /usr/share/publican, not /usr/share/Publican
Twas brillig at 12:04:45 05.09.2009 UTC+02 when da...@debian.org did gyre and
gimble:
DS If I'm not mistaken, the files in /usr/share/Publican are
DS architecture-independent shared libraries, perhaps not libraries in
DS the sense of programming languages like C or Python, but still
DS libraries.
It's just a bunch of data actually. Policy recommends to use package
name in order to allow coexistence of several versions of shared
libraries, so auxiliary data for libfoo1 does not stomp on foot of data
for libfoo2.
DS Would you agree that we discuss this with people from Debian Policy
DS and fellow Debian developers on the appropriate mailing lists? I
DS understand that upstream uses an uppercase, but for me it would be
DS preferable to be Debian compliant, and if the wording is unclear,
DS to improve the policy.
I'm really sorry, but I don't have time for it now. Feel free to start
discussions (both in debian-policy and with upstream) and keep me in
CC. Please don't forget to contact all other maintainers who use
uppercase letters in /usr/{share,lib} -- I gave some examples from my
system.
Changing /usr/share/PolicyKit - /usr/share/policykit will be beneficial
in particular. Everyone will be happy changing upstream's policies
installation path.
--
http://fossarchy.blogspot.com/
pgpJLyXzviR08.pgp
Description: PGP signature
