On Jun 20, 2006, at 1:05 AM, demerphq wrote:
On 6/20/06, Ken Williams <ken@xxxxxxxxxxxxx> wrote:
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.
Yeah. In the case of M::B this will work fine because of our policy
that whatever's in core is also identically in CPAN. In the general
case you might be out of luck.
-Ken
|
