in reply to Re: Building a CPAN module with User Inputs
in thread Building a CPAN module with User Inputs

Well, he didn't say the module was only to be used with one account. There's nothing wrong (in fact, it's something I think that should be done) with modules (and programs) having defaults. I really detest programs that refuse to run before you first write a configuration file.
  • Comment on Re^2: Building a CPAN module with User Inputs

Replies are listed 'Best First'.
Re^3: Building a CPAN module with User Inputs
by ikegami (Patriarch) on Oct 28, 2008 at 10:09 UTC

    I really detest programs that refuse to run before you first write a configuration file.

    But you're ok with doing it when installing a module? The exact same prompt you'd get from the module can be given by the program.

      So, if module X needs a configuration file, any program that uses X should have build in a dialog with the user to build the configuration file? Of course, that would require the program to run with priviledges to install system wide defaults - a priviledge which usually is there by the time 'make install' is run.

      Installing system wide defaults make sense to do at install time, not at first run time.

        So, if module X needs a configuration file,

        Going in circles. I don't buy the premise that the module needs a configuration in the first place. It hinders reusability. It hinders installation. It hinders configuration. And it hinders security to put a password in a world readable file.