Randy W. Sims wrote:
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.
I'm not asking for Module::Build (or any other program for that matter) to make that determination. I'm only interested in a big fat warning that something may be wrong. In this case, I would like to have a warning that a file installed into an earlier directory in my $PATH will mask a file installed in a later directory. *I* would have the sole responsibility for a) noticing that warning, and b) doing something about it.
The collorary (script installed into a path being hidden by an earlier PATH'd binary) would be equally useful as a warning...
John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748
