David Wheeler wrote:
On Jul 3, 2006, at 10:59, John Peacock wrote:
I think Ken was suggesting that ExtUtils::Install would detect this
sort of thing and warn (like it does now for @INC), not just delete it
without asking. You typically have to rerun the same installation
with UNINST=1 after getting the warning...
I *always* run with UNINST=1, because I only want one version of a
module in @INC. But the $PATH environment variable is a different beast
altogether, because while @INC should not include paths for different
major versions of Perl, $PATH might.
Yes. What happens if I write a File::Move module with a executable 'mv'
that takes a list of files and moves them to random locations. It gets
installed with the install path for scripts pointing at
'/usr/local/bin', and there already exists in $PATH, the files
'/usr/local/bin/mv' and '/sbin/mv'. It's unknown if the file
'/usr/local/bin/mv' is a previous version of the one to be installed or
something completely unrelated. The one in sbin is the coreutils version.
What happens during install?
Randy.
