Re: upgrading Tk && CPAN.pm

[repson]

The option UNINST=1 is mentioned (but not defaulted) during initial cpan configuration. This option removes any other copies of the modules that exist in any of the multiple valid directories modules can be installed in. The option is probably safe to turn on permenantly in most situations.

To update it just type on the cpan prompt:
cpan> o conf make_install_arg UNINST=1
This will pass it to make from that point onwards.

[Jouke]

Ah. So it is possible to configure the CPAN shell to automagically update it. But shouldn't this just be 'normal behaviour'? When I have a package installed and I want to reinstall or update the package, doesn't it seem logical to replace updated files? To me it sounds more logical than keeping old files and adding new ones. In that case you have a mixed environment of old and new files, and something tells me that is not what most people would want.

Jouke Visser, Perl 'Adept'

[arhuman]

Just my to cents comment :

But shouldn't this just be 'normal behaviour'? When I have a package installed and I want to reinstall or update the package, doesn't it seem logical to replace updated files?

I think that a 'normal behaviour' may change with another person opinion.

Some people may want to install a new module and keep a previous version (for testing pupose).
Some people even find it normal to have a Perl 5.6 WITH a previous perl version.


"Trying to be a SMART lamer" (thanx to Merlyn ;-)

[Jouke]

True, but I'm talking about mixing module versions. In my case I had 800.022 stuff AND 800.014 stuff in the same directory. In case of installing 5.6 and other versions on the same machine you just choose which version you want to use with your script. I had no choice. I think that's unwanted behaviour...but you're right that
I think that a 'normal behaviour' may change with another person opinion.

Jouke Visser, Perl 'Adept'