Re: Bug#573929: ITP: libcatalyst-devel-perl -- collection of development tools for Catalyst
If I install package X, I expect the modules in there to work. I don't
want to have to manually install dependencies which were only
If I later 'use X::Y' (from package X) and get a nasty error message saying:
blah blah was not found in @INC... etc
Then there is something wrong with the package itself.
However, if the package is so designed to fail softly and tell me
what's going on, then it is acceptable to have it in recommends; so,
taking the above example, if I did 'use X::Y' and instead got the
blah was not found, please install libpackage-x-perl
Then I guess it'd be okay.
Anyway, unless someone else in the group steps up to side with you on
this, I'll side with the way we've always done things and maintain the
On Mon, Mar 15, 2010 at 2:38 PM, Marco d'Itri <firstname.lastname@example.org> wrote:
> On Mar 15, Jonathan Yu <email@example.com> wrote:
>> If someone installs a package, they expect everything included in the
>> package to work.
> I do not believe this to be true, and indeed you will be able to find in
> the archive many packages having functionalities which will work only
> after installing some other package.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> -----END PGP SIGNATURE-----