Hi, On Tue, Jul 1, 2014 at 7:37 AM, Dominique Dumont <d...@debian.org> 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 ?
The problem is that as an end user I couldn't care less that the command I use (cme) is written in perl, or it has a public module associated with it. In my particular case, I have limited space, so I regularly crawl the lib* namespace to remove unused stuff (mostly by marking as automatic). This package is confusing because despite the name, it contains a binary that I do want. > > 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 ? > >> and it should Recommend >> all the parser modules (libconfig-model-*-perl), as cme is quite useless >> without specific parser modules. > > Parser modules are targeted for specific applications and are useless without > this specific application. For instance libconfig-model-lcdproc is useless > without lcdproc. Currently, libconfig-model-perl suggests > libconfig-model-dpkg-perl, libconfig-model-openssh-perl . Which is why they should be Recommends and not Depends. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
