Re: Source package names for R libraries (and Perl, Python, Java, …).
* Piotr Ożarowski <piotr@debian.org>, 2012-02-16, 12:59:
How about a lintian complaint at info/pedantic level called
source-package-name-doesnt-match-binary-package that triggers on
single-binary source packages and where the binary name doesnt look
like a versioned library package?
Please don't. There are developers (like me) who prefer source package
names to be as close as possible to upstream's name.
Right. Such tag wouldn't match existing practice[0] in the Python world,
where some[1] upstreams take care of making their project names globally
unique.
It would be also incompatible with policy for packaging extensions for
XUL based applications[2].
[0] That said, I'm not sure how widespread this practice is.
[1] My gut feeling is s/some/most/, though again, I didn't do any
research to justify such claim.
[2] https://wiki.debian.org/Mozilla/ExtensionsPolicy
--
Jakub Wilk
Reply to: