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

use Perl

All the Perl that's Practical to Extract and Report

Testing Installed Modules: Opening a Can of Worms More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Simple (Score:2)

by acme (189) on 2006.09.18 7:42 (#50170) Homepage Journal

It was my original request. I want to make sure that things still work even though I've upgraded a module low down in the dependency tree. I don't want to solve this in every case. I don't want the moon on a stick. I just want something simple, like copying t/* somewhere during install. I was afraid of posting about it because I knew people would go overboard and get philosophical. And look what happened when Ovid mentioned it...

Reply to This
- Re: (Score:1)
  
  by DAxelrod (4649)
  
  I'm interested in the future of the module ecosystem.
  
  This was an opportunity for me to get philisophical, but it wasn't your fault. :)

Get More Comments

Reply

Disclaimer: I work at the reg*.{[hc],sym} like a novice alchemist:
I pour the blue liquid on the red liquid. If it doesn't blow up on my
face, I proceed to turn up the flame under the blue liquid, and so on.
I have very little idea of what I am really doing, I just like the
pretty colors :-)
-- Jarkko Hietaniemi

use Perl

All the Perl that's Practical to Extract and Report

Navigation

Testing Installed Modules: Opening a Can of Worms 2 Comments More | Login | Reply /

Please Log In to Continue

Simple (Score:2)

Re: (Score:1)