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

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.
  • if ( !-t STDIN ) {
        $do_not_prompt              = 1;
        $do_not_install_permanently = 1;
    }

    Or something like that. You would think we toolchain developers would get tired of people yelling at us :)

  • Set the CPAN configuration option build_requires_install_policy.
    • How about the owner of that module defaults it for me, instead?

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
      • How should the module author know what your installation policy is --- do you prefer to keep your system as small as possible by not installing unnecessary modules (see build_requires in the META.yml spec), or do you rather like to install everything?
        • The authors of the installation framework should know that interactive questions should not be asked at install time.

          --
          J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
          • See this thread title. You can set this CPAN.pm config var to "yes" or "no", and you will never be asked. Currently it's probably "yes/ask" or "no/ask".
  • "This is the third time in under 24 hours I've temporarily downloaded and built this particular module, are you sure you don't want me to install it, permanently?"
    • I've been thinking a bit about this, and I'm wondering if it wouldn't be a good idea to have a middle ground: semi-permanently installed modules, or a more permanent CPAN cache, one that isn't emptied so often when CPAN.pm tries to save space by removing distributions from its cache. CPAN.pm could automatically store modules there that are only required to run tests, without asking. The more often a module is used, the more "sticky" it becomes, thus, less likely to be removed. A module that hasn't been used