http://qs321.pair.com?node_id=1193045


in reply to Re^3: System vs. User module version of List::Util
in thread System vs. User module version of List::Util

Well, that worked locally...

me@office:~$ locate List/Util.pm /home/me/.cpan/build/ExtUtils-MakeMaker-7.24-adRDIa/bundled/Scalar-Lis +t-Utils/List/Util.pm /home/me/.cpan/build/Scalar-List-Utils-1.45-zv9hHr/blib/lib/List/Util. +pm /home/me/.cpan/build/Scalar-List-Utils-1.45-zv9hHr/lib/List/Util.pm /home/me/perl5/lib/perl5/x86_64-linux-gnu-thread-multi/List/Util.pm /usr/lib/x86_64-linux-gnu/perl/5.20.2/List/Util.pm

but not remotely...

fantasy@fantasy.xecu.net [~]# locate List/Util.pm -bash: locate: command not found
No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!
Lady Aleena

Replies are listed 'Best First'.
Re^5: System vs. User module version of List::Util
by hippo (Bishop) on Jun 18, 2017 at 10:20 UTC

    It's 2017. A general-purpose server without "locate" installed has not been properly set up. Ask your sysadm to install it (from the package manager if there is one - on RedHat etc. the package is mlocate), run updatedb and try again.

    Of course, if you installed the newer List::Util on both boxes in precisely the same way then the module will be in precisely the same location. Did you look in /home/me/perl5/lib/perl5/x86_64-linux-gnu-thread-multi/ on the remote server?

      'A general-purpose server without "locate" installed has not been properly set up.'

      This isn't true, for various reasons. Not everyone runs a 'general purpose' server for basic hosting. Minimal packages/systems reduce potential problem surfaces and maintenance required. Regardless the topic of OPs perceived problems with their hosting provider have a long history, predating your account creation. Sane courses of action have been discussed many times and ignored.

        Minimal packages/systems reduce potential problem surfaces and maintenance required.

        No argument with that. It's just that locate is so universally useful that for me it makes it onto the Minimal Packages list. It's also sufficiently trivial in action and uses so few libraries that (again, IMHO) it does not overly expand the attack surface.

        In heading off to CPAN to investigate further, I find a stack of modules (File::Locate::Harder not being least among them) which provide the locate facility. None that I can find, however, provide the database-creation side of it. That might be a worthy project for a rainy day.

      locate was not helpful at work when I worked with CentOS 5 (or, 6 perhpas) for its database was not maintained enough (NFS mounts; stale database; changes in installed software, etc.). find was the only logical choice to locate any thing that I cared about with certainty.

      hippo, Xecu.net is set up very different from my computer.

      • Xecu.net uses cpanel 64.0 (build 24). I use Debian 8 (codename: jessie).
      • On Xecu.net, my home dir is /www/fantasy, on my computer my home dir is /home/me.
      • When I install modules into my dir on Xecu.net, I use a web interface. When I install modules on my computer, I use the command line.

      So, nothing is the same between my Xecu.net account set up and my local set up.

      No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!
      Lady Aleena

        "Xecu.net uses cpanel 64.0 (build 24). I use Debian 8 (codename: jessie)."

        CPanel isn't an operating system.