Re^2: common non-explicit dependencies besides LWP::Protocol::https ?

Thanks to you all for educating me about "suggests". Now I can go back and figure out how this analysis was run, and figure out how much additional baggage would be required if I included all of the "suggested" modules.

Comment on Re^2: common non-explicit dependencies besides LWP::Protocol::https ?

Replies are listed 'Best First'.
Re^3: common non-explicit dependencies besides LWP::Protocol::https ? by admiral_grinder (Pilgrim) on Jul 09, 2015 at 15:21 UTC
You shouldn't have to include all the suggested modules. As you said, this just happened to one of your customers in the field. They probably gave a configuration that triggered it such as providing a HTTPS URL to connect to something. Your test plan may have overlooked that so there is a hole in the test plan. I'm going to assume that during your build routine, there is a scan of the code or read prepared file listing the dependencies. Sounds like you need to modify that to add the suggested ones to the top level dependencies list.	[reply]
Re^3: common non-explicit dependencies besides LWP::Protocol::https ? by Anonymous Monk on Jul 09, 2015 at 07:05 UTC
Hi:) Some more specifics CPAN::Meta::Spec#dynamic_config, https://metacpan.org/pod/CPAN::Meta::Spec#Prerequisites-for-dynamically-configured-distributions ... cpanfile/cpanm/carton	[reply]