in reply to Configuration files

YAML and most Config:: modules from CPAN are pure Perl. You can use them from your script private directory (see use lib) without installing anything in a system location.

Replies are listed 'Best First'.
Re^2: Configuration files
by keyslapper (Novice) on Jan 01, 2005 at 18:11 UTC
    Yes, but as I neglected to mention initially, at least one of the scripts in question will be a widely distributed script under the control of sysadmins with their own concerns. It has to be system only perl or a reinvented wheel.

    I will probably check the YAML and Config:: modules to see if any are already used by the projects my other script is geared toward, but I do need the most secure system only method I can get hold of.
      How does its being distributed affect this? Presumably the admins have measures to untar a file remotely, yes? Just place the module files in the directory the script is in and have people run from there or set their perl include paths.

      But I agree with what other people have said about how not being able to install stuff is based on the wrong reasons. In the general case you *will* eventually want to use other people's module -- or your own, in .pm files -- and it is will cost your employers money not to allow you to do that.

        Agreed. Problem is I personally have no access whatsoever to the environment the script is expected to run in. The Perl installation is homogenous over a network of hundreds of machines, so getting it upgraded or modified is a serious undertaking - not that it isn't automated in some way, just that changing something on so many systems is not done lightly - nor should it be.

        If I want something included as a dependency of the project, I pretty much have to include it as part of the project. I probably have the option of simply including the .pf file in the CVS package, but then I have a lot of questions to answer concerning duplication, security of the module, etc.

        This is starting to get interesting :)