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

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.

  • Comment on Re^3: Building a CPAN module with User Inputs

Replies are listed 'Best First'.
Re^4: Building a CPAN module with User Inputs
by JavaFan (Canon) on Oct 28, 2008 at 10:31 UTC
    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.

[reply]

      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.

[reply]
        I don't buy the premise that the module needs a configuration in the first place.
        Quite a bold statement considering you've no idea what module the OP is writing. Besides, he may have a different opinion about that.
        And it hinders security to put a password in a world readable file.
        The OP mentioned a username and a software revision. He didn't talk about passwords. Besides, he wasn't asking about opinions on whether it's a good idea to ask for usernames. He just wanted to know how to ask the user a question during installation time. How would you have answered his question if instead of This will be part of the module installation. he had written This will be part of the module testing phase.?
[reply]

In Section Seekers of Perl Wisdom