[Pkg-catalyst-maintainers] Re: New packages

[Krzysztof Krzyzaniak]

Michael Alan Dorman wrote:
> Florian Ragwitz <rafl at debian.org> writes:
>> Depends on where you want to maintain them. I'd suggest pkg-catalyst. I
>> can add you to the pkg-catalyst project on alioth, if you like, so you
>> can put the packages in our svn repository.
>>
>> The other possibility is pkg-perl, but I' wouldn't prefer that as those
>> modules seem to be used by no other application than catalyst in Debian.
> 
> (Sorry for the delay in replying---this is why I want the packages
> somewhere common. :)
> 
> Certainly Test::WWW::Mechanize::Catalyst should be in pkg-catalyst.
> 
> I guess the question is what to do with the Catalyst-free packages
> that are packaged to support Catalyst packages.
> 
> For instance, Test::WWW::Mechanize, or Jemplate, which I've packaged
> in order to do Catalyst::View::Jemplate, but which doesn't have

Catalyst::View::Jemplate should go to libcatalyst-modules-perl (or 
libcatalyst-modules-extra-perl if we create one :-))

> anything to do with catalyst by itself.  Should we lobby to put those
> in pkg-perl, or assume that pkg-catalyst is as good as anywhere?

Generaly my rule of thumb is that if modules is needed to package some 
stuff for Catalyst I put this into pkg-catalyst (for example all 
packages needed to run libdbix-class-perl).

   eloy
-- 
-------e-l-o-y-----------e-l-o-y- at -t-r-a-n-s-i-l-v-a-n-i-a-.-e-u-.-o-r-g------

        jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej