Re: CPAN testers machines that lack Module::Build
Ken Williams wrote: On Mar 13, 2007, at 8:38 PM, Sébastien Aperghis-Tramoni wrote: Jonathan Rockway wrote: Why don't y'all just use Module::Install? It handles build_requires, AND you can bundle modules with your dist, in case dependencies worry you. Problems solved. OTOH, Module::Install (and Module::Build as well to be honest) doesn't work on old Perl. Some people may care about this and thus not use M::I, others may not. Module::Build works as far back as perl 5.005_03 - before that and we'd be pulling our hair out more than we already are. That said, testing on old perls doesn't always happen as often as we'd like, so sometimes it breaks and nobody notices. But generally it should work. I now remember that part of the problem were some modules Module::Build use, which are now compatible with Perl 5.004, so I'll test again Module::Build with the old Perl I have. -- Sébastien Aperghis-Tramoni Close the world, txEn eht nepO.
Re: CPAN testers machines that lack Module::Build
Jonathan Rockway writes: Why don't y'all just use Module::Install? As has been mentioned before on this list, because it involves bundling an installer with your module. So if the installer changes (to fix a bug that affects the ability of (some) end users to install your module), you have to redo your distribution. Which for some people is fine, and, on balance, their prefered way of working. But it doesn't suit everybody. Smylers
Re: CPAN testers machines that lack Module::Build
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. -- Johan
Re: CPAN testers machines that lack Module::Build
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
