Re: When to bundle Perl with your app?

Well sounds like a good approach against dependency hell ...

( though Mojolicious has the reputation to have only few dependencies ... so the answer correlates with the number of additional modules your app depends on )

Cheers Rolf

( addicted to the Perl Programming Language)

Comment on Re: When to bundle Perl with your app?

Replies are listed 'Best First'.
Re^2: When to bundle Perl with your app? by wollmers (Scribe) on May 28, 2014 at 12:16 UTC
Mojolicious has nearly no dependencies declared, i.e. perl 5.10.1 and ExtUtils::MakeMaker 0, but has many on core modules. Also Mojo has many (undeclared) suggests or recommends dependencies, which are required in an string eval. A few weeks ago I got in the dependency hell with Mojolicious: Something working for a long time (using the dump helper in a template) threw an error. Seems that another installation of a CPAN module required an explicit minimal version of Data::Dumper. But at the time of installation Data::Dumper was broken. This took me some hours to try, diagnose, and update. Yes, if someone is paranoic against such (extremely seldom) situations, then it is a good approach. But in most cases such approaches waste resources.	[reply]
Re^3: When to bundle Perl with your app? by DrHyde (Prior) on May 30, 2014 at 11:10 UTC
Mojolicious itself might have few dependencies, but any non-trivial application that you write using it will have loads.	[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks