(skip pathetic excuse about why I thought I should install Bundle::CPAN). At 5:45 PM -0500 1/3/00, Paul Schinder wrote: >It's probably a new one he installed by hand struggling to install >the Bundle. Yep. > I don't remember if I ever sent Graham a patch for this >or not. Someone probably should, even though it's just a minor >annoyance. > >> >> >> >Drag your site_perl folder to the trash. Reinstall *only* cpan-mac. >> >Whatever you need is in there. Do *not* attempt to install >> >Bundle::CPAN. You can, if you want, upgrade CPAN.pm itself to 1.51 >> >("install CPAN"). >> >>Well, some people have lots of extra modules. As he has used Mac::Glue, he >>probably has a lot of glue files in there. I would not recommend just >>trashing it. However, running the installer from cpan-mac should overwrite >>the bad files he has in there, overwriting the existing ones. > > >In general, yes :-) But he said that this was a "basic install", so >I assumed he didn't have anything else installed. That's true for my home install. Cpan-mac created my site-perl there. > >> >>The other option is to make note of modules he has installed separate from >>cpan-mac (like Mac::Glue) and save them or reinstall them after getting rid >>of site_perl. > > >Right. If there's anything worth salvaging, replace "drag to Trash" >with "restore from backup". Or, as you say, just rerunning the >installer should do it. I did make a backup on my work machine. So I can certainly use that even if rerunning the cpan-mac installer doesn't fix it... (skip long complicated story about installing Y2K fix ANNOUNCED TODAY for company mail client on 45 machines that prevents my machine having enough memory to run MacPerl right now). -Jeff Lowrey ==== Want to unsubscribe from this list? ==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org