Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re^2: module-starter command not found after installation

by gideondsouza (Pilgrim)
on Dec 02, 2012 at 11:21 UTC ( #1006704=note: print w/replies, xml ) Need Help??

in reply to Re: module-starter command not found after installation
in thread module-starter command not found after installation

Hey Maybe you're on to something

I got this:

Wed Nov 28 20:17:48 2012: "Module" Test::Simple
          "installed into: /opt/local/lib/perl5/5.12.4"
          "LINKTYPE: dynamic"
          "VERSION: 0.98"
          "EXE_FILES: "
   Wed Nov 28 20:18:06 2012: "Module" HTTP::Tiny
          "installed into: /opt/local/lib/perl5/site_perl/5.12.4"
          "LINKTYPE: dynamic"
          "VERSION: 0.024"
          "EXE_FILES: "
   Wed Nov 28 20:18:12 2012: "Module" IPC::Run3
          "installed into: /opt/local/lib/perl5/site_perl/5.12.4"

Also, I can see a number of modules under /Library/Perl/5.10 and /Library/Perl/5.12, but I can't see Module::Starter here

And It seems that all my newer module installations are going somewhere wrong! How do I make them go back to the regular default location?

I checked somewhere, can I safely do this:

eval $(perl -Mlocal::lib=--deactivate-all)

Replies are listed 'Best First'.
Re^3: module-starter command not found after installation
by aitap (Deacon) on Dec 02, 2012 at 11:55 UTC

    This command will just unset some environment variables and restore PATH in your current shell. You need to edit your shell rc file (usually ~/.bashrc, check root's too) to reset changes local::lib made. You may also need to edit CPAN config, try grep -r perl5 ~/.cpan (maybe as root) to check whether you need to do it.

    You can also install modules as normal user (to ~/perl5) if you allow local::lib to create the overlay.

    Sorry if my advice was wrong.
      OK!!! It seems like removing this line from .bash_profile worked:
      export PATH=/opt/local/bin:/opt/local/sbin:$PATH

      I installed Module Starter again and it deleted files from somewhere, installed and now I can use

      Thanks a TON all you guys! :)

        You should be asking yourself why export PATH=/opt/local/bin:/opt/local/sbin:$PATH was in your .bash_profile. It was there for a reason. Your cure might have broken something else.


      Hey thanks for your reply.

      I don't have .bashrc but I have .bash_profile and the following in it:

      source ~/perl5/perlbrew/etc/bashrc export PATH=/opt/local/bin:/opt/local/sbin:$PATH

      Should I remove the export or even the source line?

      What should I look for and edit in ~/.cpan ??

        Do you use system Perl, or Perl built using perlbrew? What's inside ~/perl5/perlbrew/etc/bashrc? Do you see any differences in root's config files? Search ~/.cpan/CPAN/ and the output of o conf CPAN shell command for something unusual in options named make_..._arg and mbuild_..._arg.

        It looks like removing these lines made you use system Perl again instead of perlbrew's one, and CPAN is set to install modules in system directories by default.

        Sorry if my advice was wrong.
      This is in reply to @davido's post, I can't seem to reply directly to his post.

      Yes, some book I was reading had a thing about local::lib and I barely understood it well and added that export PATH in my bash_profile myself.

      I tried to run a bunch of scripts and my dummy catalyst projects, and they work so, so far so good :)

      When I did perldoc perllocal I get an output described in this post : Re^2: module-starter command not found after installation. I'm assuming those are modules installed in my local lib and if I need them I might have to do a re-install?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1006704]
[choroba]: No, if there are no threads, then the user wants to use MCE. If there are threads, the user can choose.
[1nickt]: choroba Understood. I'm wondering about the logic in a cpanfile. If the perl doesn't support threads, it's easy: require MCE. If the perl does support threads, as you say the user has a choice, so require both? Or, assume that irrespective of the choide
[1nickt]: ... choice, the threaded-perl user *probably* wants to use threads, therefore only require threads and leave MCE out, allowing the user to manually install if desired?
[choroba]: just require any of MCE and threads. Not sure if that's possible in the cpanfile, but should be possible early in the Makefile
[1nickt]: The app expects threads as default anyway, right?

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (12)
As of 2017-10-18 13:20 GMT
Find Nodes?
    Voting Booth?
    My fridge is mostly full of:

    Results (244 votes). Check out past polls.