in reply to Re^2: Permissions for a separately installed perl
in thread Permissions for a separately installed perl

Ok, in that shell, what does

perl -e 'print "$]\n";'

yield?

The shell hashes paths to commands, and if you add a command to a path previous in $PATH to the already hashed one, your may not see the changes:

qwurx [shmem] ~> touch blorflydick qwurx [shmem] ~> rm blorflydick qwurx [shmem] ~> mkdir bin qwurx [shmem] ~> PATH=$HOME/bin:$PATH qwurx [shmem] ~> which rm /bin/rm qwurx [shmem] ~> echo '#!/bin/sh' > bin/rm qwurx [shmem] ~> echo 'echo no rm damnit' >> bin/rm qwurx [shmem] ~> chmod a+x bin/rm qwurx [shmem] ~> which rm ~/bin/rm qwurx [shmem] ~> rm blorflydick rm: cannot remove `bloflydick': No such file or directory qwurx [shmem] ~>

A new shell will see the changes, however:

qwurx [shmem] ~> echo $SHLVL 4 qwurx [shmem] ~> bash qwurx [shmem] ~> echo $SHLVL 5 qwurx [shmem] ~> rm blorflydick no rm damnit qwurx [shmem] ~>

Replies are listed 'Best First'.
Re^4: Permissions for a separately installed perl
by almut (Canon) on Feb 28, 2010 at 13:53 UTC
    A new shell will see the changes

    or

    $ hash -r

    to make bash forget its cached bindings.

      Yes!
      $ perl -v This is perl, v5.10.1...
      Many thanks for your efforts.