As a concrete example, I habitually install App::Ack with the perlbrew-installed cpanm (i.e. after running perlbrew install-cpanm).
The problem: perlbrew list-modules does not show App::Ack. Instead, all it sees is the binary ack. This does not exist as a package, so then something like
$ perlbrew clone-modules old@lib new@lib
inevitably fails to install App::Ack because the latter is simply not listed. Instead, I get a message that cpanm has tried to find ack (the binary!) and couldn't:
! Finding ack on cpanmetadb failed.
! Finding ack () on mirror http://www.cpan.org failed.
! Couldn't find module or a distribution ack
Of course, the other option for reinstalling modules doesn't work either:
will fail for the same reason that App::Ack is not listed by the first command.
I'm not sure what the root cause of this is: is it a perlbrew issue or a cpanm problem? Does cpanm itself somehow fail to properly register App::Ack as an installed package?
As a concrete example, I habitually install App::Ack with the
perlbrew
-installedcpanm
(i.e. after runningperlbrew install-cpanm
).The problem:
perlbrew list-modules
does not showApp::Ack
. Instead, all it sees is the binaryack
. This does not exist as a package, so then something likeinevitably fails to install
App::Ack
because the latter is simply not listed. Instead, I get a message thatcpanm
has tried to findack
(the binary!) and couldn't:Of course, the other option for reinstalling modules doesn't work either:
will fail for the same reason that
App::Ack
is not listed by the first command.I'm not sure what the root cause of this is: is it a
perlbrew
issue or acpanm
problem? Doescpanm
itself somehow fail to properly registerApp::Ack
as an installed package?