On 6/20/06, Ken Williams <[EMAIL PROTECTED]> wrote:
On Jun 19, 2006, at 6:37 PM, Ron Savage wrote: > On Mon, 19 Jun 2006 14:32:10 +0200, demerphq wrote: > > Hi demerphq > >> Nope. If you upgrade it should go in to site/lib, meaning you have >> to use UNINST=1 if you upgrade. > > Are you sure it'll go into site/lib? We may be confusing the two kinds of upgrades - upgrading perl from 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.
Reinstall the module with UNINST=1.
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.
Yes thats normal. And what happens with DD or other core modules being upgraded. UNINST isnt needed on Win32 except to handle the case of a core module being upgraded. -- perl -Mre=debug -e "/just|another|perl|hacker/"
