NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
There have indeed been some CPAN problems (Score:2)
So firstly, no guarentees if you have more than one Perl installed... no Perls really live together well.
Secondly, there's known issues in CPAN.pm.
I recommend uninstalling the July strawberry and trying again with the new October release.
http://strawberry-perl.googlecode.com/files/strawberry-perl-5.10.1.0.msi [googlecode.com]
This has a new (dev) CPAN release that might fix your problem, and some updated Perl modules and C libraries that should (hopefully) make the installation much easier.
Finally, yes, newbies are not REALL
Re: (Score:1)
I submit that almost anyone installing strawberry already has a perl, and likely more than 1.
When I install strawberry, I have activestate, cygwin, and I tried building my own. And after that, I have an old strawberry in front of the new strawberry.
A prominent set of warnings seems appropriate.
Re: (Score:2)
The way I solved that is as follows:
I removed the Strawberry specific paths from the
PATHenvironment variable. I then added an icon in the start menu to launch a console shell (cmd.exe), after prepending these paths toPATHfirst.One easy way to do that, is by making a BAT file with the following contents:
But an IMHO nicer alternative is to just create a shortcut with this as the target:
Re:There have indeed been some CPAN problems (Score:2)
I just found there's a
padre.exefile in theperl\bindirectory, with the same modification time aspadre.bat. Apparently they were built together. So that's why it doesn't need a console window...Reply to This
Parent