Bug#752797: libconfig-model-perl: Should split library from command

[gregor herrmann]

On Tue, 01 Jul 2014 13:37:50 +0200, Dominique Dumont wrote:

> On Thursday 26 June 2014 13:00:52 you wrote:
> > The lib*-perl namespace is (or at least should be) for perl libraries, not
> > for end user binaries.
> > 
> > The cme command should live in its own package,
> 
> Err, why ? What is the problem you're trying to solve ?
> 
> Some people will argue that a new binary package will be created for a small 
> script.
> 
> What do people on debian-perl think ? Should cme live in its own binary 
> package ?

I'm a bit ambivalent ...

On one hand, I also think that a separete package for a script which
then depends on on the rest anyway is overkill and bloats the
Packages file and everything.

On the other hand, for non-perl maintainers the information might be
easier to "install cme and then run `cme check dpkg'" than "run `cme
check dpkg', oh, cme is in libconfig-model-perl, and you also need
libconfig-model-dpkg-perl". (If I got the package names right now :))


Cheers,
gregor 

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: David Bowie: Under Pressure
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 928 bytes
Desc: Digital Signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20140702/d212cd2f/attachment.sig>