Subject: | cpanp shell exits with error "No such module: Terminal>" |
I have added my installed perl's bin\ folder to my PATH and am trying to
start the cpanp shell by simply typing "cpanp" in a standard cmd.exe
command prompt on Windows 7.
The cpanp shell immediately exits with an error if I try to enter it
with my current directory being on the C: drive:
##########
C:\Temp>cpanp
CPANPLUS::Shell::Default -- CPAN exploration and module installation
(v0.9130)
*** Please report bugs to <bug-cpanplus@rt.cpan.org>.
*** Using CPANPLUS::Backend v0.9130. ReadLine support disabled.
*** Type 'p' now to show start up log
Did you know...
You can turn off these tips using 's conf show_startup_tip 0'
[ERROR] 'Terminal>' does not contain an author part
[ERROR] Cannot find 'Terminal>' in the module tree
No such module: Terminal>
No modules found to operate on!
Exiting CPANPLUS shell
C:\Temp>
##########
If I switch to seemingly any other drive letter then it works fine:
##########
C:\Temp>K:
K:\>cpanp
CPANPLUS::Shell::Default -- CPAN exploration and module installation
(v0.9130)
*** Please report bugs to <bug-cpanplus@rt.cpan.org>.
*** Using CPANPLUS::Backend v0.9130. ReadLine support disabled.
*** Type 'p' now to show start up log
Did you know...
You can use wildcards like '*' and '2..5' on search results
CPAN Terminal>
##########
This is most unfortunate since I normally work on the C: drive :-(
I have an identical problem with CPAN's cpan shell (see CPAN RT#79001),
so the problem must lie elsewhere (Term::ReadLine?), but I'm reporting
the bug here anyway because I guess if a fix is made elsewhere then
you'll want to add a prerequisite minimum version on the updated dependent.