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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Which module had too many requirements? Or, which thread? I tend not to follow perlmonks (it's not my style of interface; needs more of a usenet / mailing list approach for me to like it; same with slash really).

    People often complain that some of mine have too many requirements, but I generally don't pay attention to them. I use the modules because they make my life easier.

    I can live happily whether they install my module or not. (I think Ask mentioned that WWW::Shorten had a number of requirements, most
      ---ict / Spoon
    • It was in the chatterbox. I think it was Net::SSH::Perl or something like that.

      But the issue isn't really that it has too many prerequisites. For the audience I'm talking about, even one prerequisite (that they then have to install) is too many :)

      • I'm not entirely fond of ExtUtils::AutoInstall in a Makefile.PL of a module, but I do like it in the Makefile.PL of an application. Mind you, not enough applications come with Makefile.PLs.

        I can happily see that such things are necessary. I'm just a snob about my (somewhat crappy) modules and programs =)

        Like many of those reading, I upgrade my modules regularly. I run 5.8.0.

        Perhaps unlike many of those reading I find it irritating when someone writes a workaround for a bug that was eliminated over 2 years ago rather than have people upgrade the module in question. If they're not going to expend effort, why should I? Sure, they may not know enough. Or things may not be easy enough. But will it ever be? Will they ever know enough? Do they give a damn?
          ---ict / Spoon