|Don't ask to ask, just ask|
Re^5: Architecture-specific module conflicts under perlbrewby karlgoethebier (Vicar)
|on May 17, 2013 at 07:49 UTC||Need Help??|
"I posted that as an example of things generally going wrong, rather than as a specific glitch to overcome."
This is, cautiously said: a "funny approach". Isn't PM (partly) about "overcoming glitches"?
When i discovered perlbrew, i thought this is heaven-sent. But i'm skeptical about "this is the promised land" stuff.
So i installed it on different boxes, played around with it, tried to break it, did some insane things.
But it didn't break. It worked.
So i recommended it for a box that is a good part of my job. The box is for monitoring more than 120 hosts with more than 1000 services.
Setup and testing lasted about 3 month. And many people are relying on this box. And i recommended the tool on PM.
So, if someone comes and says: "That stuff you recommend doesn't work as expected!" the bells ring.
I try to understand why and how to find a solution.
If i where you (assuming you are still interested in using perlbrew) i would throw away that whole stuff and start over again with a fresh setup, doing it exactly as described in the docs.
If you can reproduce the issue, contact the author. I'm shure you get help - many rely upon perlbrew.
Best regards, Karl
P.S.: Ever had a broken Perl? No? So you are lucky. I had it one time on a Mac OS X server.
I fired up cpan and went for lunch or so.
When i was back, i had another Perl installed, tons of modules uninstalled and tons of modules new installed.
The box was unuseable - and it was not for testing purposes.
«The Crux of the Biscuit is the Apostrophe»