Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

Alias
  (email not shown publicly)
http://ali.as/

Journal of Alias (5735)

Wednesday October 31, 2007
07:12 PM

Moving away from Module::Install for ::Tiny modules

[ #34807 ]

Sébastien Aperghis-Tramoni filed a bug for Module::Install/YAML::Tiny complaining that Module::Install is preventing YAML::Tiny from being fully 5.004-compatible.

And to be honest, he's complete right in his fear and loathing.

Using Module::Install (or even Module::Build) is a complete philosophical clash with the entire concept of ::Tiny. OBVIOUSLY we should be using the oldest, most stable, most compatible build system of all, for modules which have practically no features and absolutely no complexities by design.

So as soon as I get a chance, I'm reverting the installers for all of the ::Tiny modules to plain vanilla ExtUtils::MakeMaker.

And my apologies to the beleaguered Sébastien.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don't use Windows, but don't Windows users have to download and install a specific make utility in order to use MakeMaker to install modules?

    • 1. Nobody is using 5.005 on Windows.

      2. Everybody that matters is now using Strawberry Perl, and doesn't have to download anything. :)

      3. Anyone that isn't, should probably be using PPM files, and the ActiveState build farm is the only thing that needs make.

      • Can Strawberry install TT on Windows?
        • Is this a trick question? :-)

          I just installed SP and TT (for Catalyst) twice this week on win32 without any problems. (one a real win32 machine, and one in XP in parallels
          • No. I have not used SP and had read (might have been a while ago) that TT was an issue. Or at least I thought it was TT or maybe it was DBD::Oracle come to think about it.
            • TT did have some issues on Win32 not long ago but they have been fixed.
            • The problem was on all Win32, not just Strawberry.

              The TT issues are quite fixed now, and Andy has started releasing test releases to the mailing list first, for Win32 people to check, before he does the uploads.
      • That makes sense, although your first and second rules sound awfully close to mine.

  • maybe its me but today i tried it as an drop in replacement and it failed so far for 2 reasons. 1.LoadFile did not return a ref but thou count of the arraylength. 2.empty list nodes as i use for seperator in menu definition are undef instead just empty ('') like in the original YAML. but the idea is great :)
    • If you have examples of documents that are incompatible, please report them and I'll look into it.
      • this is a menu definition. you see the arrayitems with no content. the varialble that holds that nothing i want to be empty not undef. i don't know if its accidental and breaking his own specs, but that the way i used to get the input from YAML Parser. BTW: hope you read my last mail. your changes are now all in but switch to new config path handling needs some tweaks before i uncomment them all.

        main_toolbar:
          - item file-new
          - item file-open
          - item file-print#
          - item file-close#