in reply to Task:: or Bundle::

Task:: modules that are uploaded to CPAN are not necesarily suitable to hand-installing in the way that you want.

On the other hand (and this is the entire point of Task::) you can use anything that the CPAN configuration module (in this case Module::Install) supports.

For your situation, try putting the following extra command just before WriteAll.

auto_install;

This will cause some extra magic to be bundled into the installer that will spawn off a CPANPLUS instance that DOES do the automation of mass module installs that you want.

Of course, this assumes you aren't uploading to CPAN. If you are uploading to CPAN, auto_install can still be a bit buggy (it's supposed to silently degrade when running inside an existing CPAN client, but breaks sometimes still) so it's strongly recommended not to use auto_install for modules that are uploaded to the CPAN.

Replies are listed 'Best First'.
Re^2: Task:: or Bundle::
by brainsick (Sexton) on Mar 14, 2007 at 12:27 UTC
    It's not that I want to hand-install modules. I'm absolutely comfortable using CPAN.pm as the means of automating the install of either a Task:: or a Bundle::, I just didn't understand that it was necessary.

    What really screwed me up was this statement in the Task POD:
    This implementation as a module allows normal Perl tools to be able to load the module and check it's version to confirm you have the required modules, without the need for a CPAN client involved.
    I interpreted that as "CPAN.pm isn't necessary for Task::s". Let's touch up the Task POD to clarify that CPAN.pm use is still appropriate, and even expected, for automated prerequisite resolution.

    I still have the larger question of where the "Perl community" is headed. If there's any kind of consensus that Task:: is preferred over Bundle:: then let's add that to the CPAN FAQ or even to the CPAN.pm POD. I stumbled on Task:: entirely by accident!
[reply]

In Section Seekers of Perl Wisdom