Re^2: Installing Template::Toolkit on Windows

[davies]

Oh, I wasted LOTS of time doing this. :-) I think, had I known how to do it, it wouldn't have taken much longer than your 2 minutes. The two 20 minute waits (and I didn't time them accurately - that's an estimate) were for the installation of the C compiler and ?make utility. Without that the computer time would have been much shorter. But even the 40 minutes for that was only a small part of the time I wasted not knowing what to do and googling frenetically. That's why I thought it might be worth putting up the OP in case someone found themselves in the same boat.

I'm interested to see you using wget instead of the two tools I'd heard of previously. Is this documented anywhere? Especially, is there any documentation on which to use and when? As I stated in the OP, the only ones I've ever tried are PPM and the CPAN shell (I've also used Debian's apt-get on the Pi).

Regards,

John Davies

[BrowserUk]

I'm interested to see you using wget instead of the two tools I'd heard of previously. Is this documented anywhere?

wget is just a GNU download tool -- you can get a binary version for Windows from here -- but you can download the tar.gz using any other tool or method including just clicking the link on the CPAN website for whatever package you want.

I long ago gave up on CPAN(P/plus/whatever) because they:

• insist downloading stuff that I neither need nor want;

  Like some ancient version of nmake that hasn't worked for building perl modules since pre-5.6.1 days. If then. It is well-known that it is a pointless exercise to install that; but still the CPAN shell will insist on downloading it even when there is a working, up-to-date version already installed and available via the path! Shear bloody-mindedness.

• Insist on installing alternative compiler & tool chain that don't work, rather than using the already installed compiler that does, simply because the broken algorithm they use to look for the compiler -- that does everything but the sensible thing of searching the path -- cannot find it.
• Insist on trying to provide a broken emulation of *nix command line history functionality; when my shell has its own history facility -- that works -- built-in.
• Insist on fucking with my carefully chosen shell color settings in order to try and highlight random bits of output in random colors according to no discernible pattern; and rendering the output entire unreadable in the process.