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.
  • Looking at the MOTIVATION section of
    Module::Build's man page, I don't think you see
    any of the concerns of the problem of
    installation as outlined here. It was a more
    limited fixing of the problem of make and EU::MM.

    When did the issue of the problems of software
    users as distinct from software developers start
    to arise? After the availability of and
    so on made it even easier than it had been to
    install modules?
  • Well, the problems have been there the whole time.

    The reason it hasn't come up sooner is that installer deficiencies of this nature are creeping problems.

    They build up gradually, and only start to impact strongly as the number of MB packages increases, and as the number of production versions of MB increases.

    As long as few people are using it, and it isn't changing quickly, you have a Pattern 1 situation. The installers don't break if the installer infrastructure is static.

    Add to that that most 9 out of 10,
  • I think this taxonomy is lacking because it confuses several different tasks:

    • Package management -- managing available/installed software and retrieving software to be installed from a repository
    • Installation -- putting pieces of code/library into OS/user-specific locations for later use
    • Configuration management -- telling installers how to do their jobs
    • Distribution creation -- creating bundles of code, configuration, and -- in some cases -- an installer
    • Authoring tools -- helping authors with non-distri