Re: removing perl modules

It's not the only way, but it's likely the easiest way. It's really difficult to know exactly what a module has installed and where.

I'm not sure what you mean by "start over" though. What problem do you face that this seems like a good option?

Comment on Re: removing perl modules

Replies are listed 'Best First'.
Re^2: removing perl modules by elnino2007 (Novice) on Nov 09, 2006 at 20:41 UTC
Oh. I'm installing webgui, and they have a testEnvironment.pl script that goes through and makes sure that I have all the perl mods installed that I need. I've worked my way thru (I thought), and ran in to some problems where it's just seems like a big huge mess. It says I need to insall Apache::Request, but when it does CPAN says I have it (and I believe I do), then there is the fact that I have two mod_perls installed at different versions and one is 32-bit and the other 64-bit (I'm on a 64-bit system) one via yast, and one via cpan. So then I started removing stuff from Yast, and I'm probably really hosing this all up.	[reply]
Re^3: removing perl modules by chromatic (Archbishop) on Nov 09, 2006 at 21:13 UTC
Yeah, you're probably hosting it up. The one trick I've always had to remember is to use the appropriate Perl related to the mod_perl instance I want to run. There's always a Perl binary somewhere associated with the mod_perl installation; run the CPAN shell or the test script with that binary and install the modules for that installation. I don't think removing things will help you that much, unless you are very sure to remove one complete mod_perl installation and its entire related Perl installation.	[reply]