|Welcome to the Monastery|
Re: Should cpanminus be part of the standard Perl release? -- MSWin32by Discipulus (Abbot)
|on Jun 06, 2018 at 11:17 UTC||Need Help??|
dear marto and all,
I used cpanm client and it's cool and a has a cleaner interface and some interesting experimental features, notably the ability to uninstall modules, not available in the classic cpan classic client.
But, as stated above by Tux with reason a Linux fan, cpanm it's not fully functional on MSWin32 and this is very common for many genial pieces of code by miyagawa. If this is acceptable for example for some webserver PSGI aware (even me I'd put on linux only) it's not for the client used to install modules.
We can like or dislike MSWin32 OSs but they are here and they have big slice of the market. I'm not a fan but I work with it daily so I must be very careful in my choices. I jumped on the strawberry perl charriot many years ago and I'm very happy with it: now I can use perl on MSWin32 the very same way I can use it on linux.
Let's see something:
Noticed the path? Is not File::Spec a core module since years?
Is not the case to translate directory seprators? or to use quotemeta and qr and eval the regex? Ok it' just an alias fo cpanm App::cpanminus but the latter works fine: App::cpanminus is up to date. (1.7044)
Let's test some module:
Ouch it's my cpanm configuration wrong or broken?
Mah? I have all! let's try dear old cpan
So, in conclusion, every better, modern, client upgrade will be welcome if it runs as well and everywhere as the older one.
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.