I spent much time to find the package. I even thought to build the
package by myself, but apt-file helped me to find the package.
Traditionally perl modules are named as lib<module-name>-perl [1]
so It would be nice to rename the module to
libtwiggy-perl
The module aslo contains /usr/bin/twiggy. It could be left
in module 'twiggy'.
So It would be nice to have two packages:
twiggy:
depends -> libtwiggy-perl
contains ->
/usr/bin/twiggy
/usr/share/man/man1/twiggy.1p.gz
/usr/share/doc/twiggy/copyright
/usr/share/doc/twiggy/changelog.gz
/usr/share/doc/twiggy/changelog.Debian.gz
libtwiggy-perl:
contains ->
/usr/share/perl5/Twiggy.pm
/usr/share/perl5/AnyEvent
/usr/share/perl5/AnyEvent/Server
/usr/share/perl5/AnyEvent/Server/PSGI.pm
/usr/share/perl5/Plack
/usr/share/perl5/Plack/Handler
/usr/share/perl5/Plack/Handler/Twiggy.pm
/usr/share/perl5/Twiggy
/usr/share/perl5/Twiggy/Server.pm
/usr/share/perl5/Twiggy/Server
/usr/share/perl5/Twiggy/Server/SS.pm
/usr/share/man
/usr/share/man/man3
/usr/share/man/man3/Twiggy.3pm.gz
/usr/share/man/man3/Plack::Handler::Twiggy.3pm.gz
/usr/share/doc/libtwiggy-perl/copyright
/usr/share/doc/libtwiggy-perl/changelog.gz
/usr/share/doc/libtwiggy-perl/changelog.Debian.gz
1. http://www.debian.org/doc/packaging-manuals/perl-policy/ch-module_packages.html#s-package_names
IIRC, at the time this was uploaded for the first time, it was decided to rename the package this way because it was mainly inteneded to be used as standalone application (as per group's policy [0]). Same goes for the starman package. This [1] is what I found with a quick search, but I couldn't find the specific discussion about twiggy and starman use. I don't think splitting the package this way makes much sense given that the twiggy script is quite minimal. In the case this is going to be renamed, the package libtwiggy-perl should just "Provides: twiggy". Cheers [0] http://pkg-perl.alioth.debian.org/policy.html#package_naming_policy [1] http://lists.debian.org/debian-perl/2011/02/msg00099.html
Ack, that matches my memory (and the group's) policy. The discussion actually came up several times during the last years, pointing out that user who look for the well-known application <app> will rather find the <app> package than the lib<app>-perl package. 2x ack. Cheers, gregor
Now the package is well alternative to libanyevent-httpd. So there will appear many projects dependig on libtwiggy-perl. :) I think that package size means little. If somebody needs twiggy script he will seek 'twiggy' package. If he needs Twiggy module he will seek 'libtwiggy-perl' package. So I think it is worth to split package anymore. Now Debian has already have one package that depends on twiggy. And it uses it as library (external module). So the project (probably) needn't twiggy script :)