On Mon, 19 Jun 2006 20:18:28 -0500, Ken Williams wrote: Hi Ken
> We may be confusing the two kinds of upgrades - upgrading perl from I suspect that's part of it - but not for me. My policy is to never do an in situ upgrade of Perl. And yes, that does mean reinstalling all modules I've downloaded. That's why I use a program to install as many of them as can be automated, and more code to scan the log looking for failures... > 5.8 to 5.10 will, as far as I know, leave you with two copies of > M::B, one in lib/ and one in site/lib/. Maybe there's a way to get > -- uninst to work when upgrading perl, but if so I don't know it. Exactly my thoughts. That's why I'm prompting for clarification from demerphq himself. > If you just upgrade M::B within a 5.8 installation, it will > continue to go into site/lib/, even if it's a version of M::B that > appears in 5.10 core. Sure. -- Ron Savage [EMAIL PROTECTED] http://savage.net.au/index.html
