Bug#484809: package naming recommendations

[Thomas Viehmann <tv@beamnet.de>]

Package: developers-reference
Severity: wishlist

Hi,

I wonder whether the developer's reference should offer recommendations 
for the naming of packages along the lines of:
- for source packages do not blindly take the name of the upstream
  tarball but consider something related to the binary package's naming
  scheme
  (rationale: namespace for source packages seems to be fairly
   polluted. In particular having binary and source packages of the
   same name seems undesirable)
- for libary packages, the package name should match with the soname
  (as checked by lintian) unless there is a compelling (non-aesthetic)
  reason not to.
  (rationale: the lintian warning seems to be a good way to
  indicate when something unexpectedly happened to the soname if the
  package started out using a name lintian does not warn about)

Kind regards

T.
--
Thomas Viehmann, http://thomas.viehmann.net/