Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

domm (4030)

domm
  (email not shown publicly)
http://domm.plix.at/

Just in case you like to know, I'm currently full-time father of 2 kids, half-time Perl hacker, sort-of DJ, bicyclist, no longer dreadlocked and 33 years old

I'm also head of Vienna.pm [pm.org], maintainer of the CPANTS [perl.org] project, member of the TPF Grants Commitee [perlfoundation.org] and the YAPC Europe Foundation [yapceurope.org].

I've got stuff on CPAN [cpan.org], held various talks [domm.plix.at] and organised YAPC::Europe 2007 in Vienna [yapceurope.org].

Journal of domm (4030)

Monday May 04, 2009
02:10 AM

Module::Install hate

[ #38921 ]

I should rather post this to we.hates-software.com, but a) I don't care for yet another subscription and b) I'm not sure if it's still running

Anyway..

From time to time I do this to update my CPAN stack:

~/$ cpanp
CPAN Terminal> x
CPAN Terminal> o
.. list of modules needing an update
CPAN Terminal> i 1 .. $last_module

As I have set up my CPANPLUS to automatically install all dependencies, this should work completely without my interaction. If I'm feeling courageous, I add --skiptest and/or --force for even less interaction.

But the comes along a distribution using Module::Install, which trys to be smart (something computers fail at more often than not) and uses its own dependency installation scheme. Which includes asking me if I want to install required dependencies.

HATE!

Not only did I explicitly tell my computer to NOT ask me, how should the dist I'm installing work if some required dependencies are missing?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 1. It only does that for modules that use auto_install, against recommendations otherwise.

    2. I tried to remove that feature entirely, but the Catalyst people forced me to put it back in because it critically broke their workflow.

    3. The bug you are reporting has already been fixed in 0.86 and Module::Install doesn't do that any more.

    4. Notwithstanding all of the above, old releases by people that use auto_install even though they are told not to, and don't do updated released, will continue to display that b

    • Notwithstanding all of the above, old releases by people that use auto_install even though they are told not to, and don't do updated released, will continue to display that bug.

      Copy and paste strikes again!

      • Indeed, but we've known all along that it was copy and paste because that was the best option we had to hand.

        Fortunately, 5.10.1 will finally change that, and we can start to look at how we make life sane again.

    • 3. The bug you are reporting has already been fixed in 0.86 and Module::Install doesn't do that any more.

      So it should be sufficient if I update inc::Module::Install?

      4. Notwithstanding all of the above, old releases by people that use auto_install even though they are told not to, and don't do updated released, will continue to display that bug. Sorry.

      :-)

      Oh, and if I sounded to harsh, this wasn't targeted at you, because I sort of remembered that this issue is caused by people using Module::Install in outdated ways.

      • Alas no, the authors of the offending modules must update inc::Module::Install and do new releases.

        But now that I'm starting to get some traction on all-of-cpan analysis and monitoring, I hope to start making some process and getting older modules updated.

  • Set "PERL_EXTUTILS_AUTOINSTALL=--default-deps". That saves a certain amount of hatred.

    -- dagolden