holli has asked for the wisdom of the Perl Monks concerning the following question:

Fellow Brothers of Perl, I have recently installed CamelPack and therefore used the cpan shell for the first time. Now I noticed that the shell does not respect the modules that are already installed (by default or via ppm) and happily writes over them.

Is there a way to get rid of this behaviour?


holli, /regexed monk/

Replies are listed 'Best First'.
Re: cpan shell and windows modules
by PodMaster (Abbot) on Feb 24, 2006 at 13:37 UTC
    Now I noticed that the shell does not respect the modules that are already installed (by default or via ppm) and happily writes over them.
    Come again (thats what it should do)? If you do 'm Module::Name' in the cpan shell, it will tell you if Module::Name is already installed, and which version ... so then you can decide if you want to install (and overwrite).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
Re: cpan shell and windows modules
by kwaping (Priest) on Feb 24, 2006 at 15:13 UTC
    This isn't a direct answer to your question, but it might help you out. The cpan shell command r will tell you if your modules are up to date or not. r by itself will go through all your modules and report on the ones needing an update, while r Module::Name will report on only that specific module.
[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom