On Mar 14, 2007, at 10:19 PM, Adam Kennedy wrote:
Johan Vromans wrote:
Jonathan Rockway <[EMAIL PROTECTED]> writes:
Why don't y'all just use Module::Install?
Because it doesn't perform a mere install, as the name suggests. It
builds, meaning it requires (and uses) a build environment -- and
scares away customers that do not want to have a build environment on
production systems.
Then again, so does EU:MM and M:B, so I'm not sure why that's a
counter-argument...
Adam K
M::B does not require make nor a C compiler to install or run, once
you have all of its dependencies installed. That means that in
theory it can be installed on a Mac that lacks the Developer Tools or
on Windows with just Perl, for example.
With M::B in core for 5.10, it will be possible to install almost any
pure-perl module from CPAN with just 5.10 and nothing else. This
will significantly simplify bootstrapping CPAN on a bare bones
machine (read: production systems).
I speak from negative experience: I tried to get a Catalyst app
running on another developer's Mac this week. I quickly realized
that without make, we were dead in the water. I suppose
M::I::Catalyst could have helped build a PAR for me that I could have
copied over, but his machine was Intel and mine was PPC so it would
have been suboptimal at best. So, we resorted to installing a build
environment via the Mac Developer Tools disk...
Chris
--
Chris Dolan, Equilibrious LLC, http://equilibrious.net/
Public key: http://chrisdolan.net/public.key
vCard: http://chrisdolan.net/ChrisDolan.vcf
