Hello again pryrt
I forgot to mention my opinion about cpanm already presented in Re: Should cpanminus be part of the standard Perl release? -- MSWin32: something is changed and now is able to test succesfully Text::Xslate but other issue are still there and so I do not suggest it for win32 users. Mainly do not handling path correctly in 2022 is... strange :)
Welcome to Strawberry Perl Portable Edition!
Perl version : 5.32.0 / MSWin32-x64-multi-thread
C:> cpanm --version
cpanm (App::cpanminus) version 1.7044 (C:\EX_D\ulisseDUE\perl5.32.64bi
+t\perl\bin/cpanm) <--------- O_O \ \ \ /?
C:> cpanm --self-upgrade
Can't find Unicode property definition "e" in regex; marked by <-- HER
+E in m/^C:\EX_D\ulisseDUE\pe <-- HERE rl5.32.64bit\perl\site\bin/ at
+C:\EX_D\ulisseDUE\perl5.32.64bit\perl\bin/cpanm line 32.
+ ^---- O_O ?!?!
C:> cpanm --test-only Text::Xslate
Successfully tested Text-Xslate-v3.5.9
Unfortunately the will to ignore win32 as a big market share seems to persist in the habits of some, even genial, dev which anyway deserve my deep respect.
If in you I'd remove completely any mention to cpanm for win32 users
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.