Re: Bug#573929: ITP: libcatalyst-devel-perl -- collection of development tools for Catalyst
On Mon, Mar 15, 2010 at 2:54 AM, Marco d'Itri <email@example.com> wrote:
> On Mar 15, Jonathan Yu <firstname.lastname@example.org> wrote:
>> previously, this module was part of libcatalyst-modules-perl, but I
>> want to move it out of that bundle because it contains many useful
>> modules even where the rest of the Catalyst modules are not needed. A
>> bare-bones installation of the Catalyst runtime + Catalyst::Devel
>> might be sufficient for developers, and it would be useful to
>> (perhaps) minimize attack surface area in case there are
>> vulnerabilities in other Catalyst modules.
> Talking about minimal systems, don't you think that many of the
> libcatalyst-modules-perl dependencies should be demoted to recommends?
> I believe it is quite plausible that many people actually need only some
> of the included Catalyst::* modules.
Well, having reviewed all the packages, they are all needed to use the
modules as part of the libcatalyst-modules-bundle. However, I agree
that the bundle itself is pretty big (and as one of the maintainers, I
can say that it's not fun to maintain either).
If you can point me to which dependencies would be suitable to be
recommends-only, I'd be happy to demote them, but I don't think that's
really possible without breaking the build/usage of said modules.