A few idle comments here:
The Unix locate command will only function if the updatedb command is being periodically run to update its database, a-n-d if the file is in a place that is being indexed by it. (For instance, NFS shares usually are not.) Windows systems do not have an equivalent.
Libraries will always be searched in the order specified by @INC, which can be managed in any one of several ways (such as use lib). But some installation scripts, which are run when you install a package for the first time, also perform these tests and may be confused by things being found in un-conventional locations. If the test is only a warning, you can proceed. But occasionally, you must “force” installation of the module to override the tests. This is your judgment call. (The OP did not provide details as to exactly when the conflict-message occurred.)