Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • Can you get a dedicated perl user that owns /usr/local/perl and install your own instance there [], where you can manage the modules yourself? Can you install your own instance as your own development user somewhere in /home or something?

    Not having access to Text::CSV_XS is ridiculous. Having to wait two weeks for it is ridiculous. Not being able to put it in a development area yourself to work with would be beyond ridiculous, but hopefully you can at least install the module somewhere you have write acce

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • Developers ought to have complete control over the development platform. This is the reason. If administrators are required to "protect" something, then that something should be production, and your organization would be well-served by formalizing the boundaries between development and production, and letting the developers have control over the development server/instance.

      I both agree and disagree with you here. Most developers do not know how to properly administer a server or even their own workstation. I don't care if they use Linux at home. Professional sysadmins have the experience in this department, and it's their job to maintain the infrastructure. And yes, having been a sysadmin for almost 12 years, I'm biased. :)

      In my experience, it's critical that developers have a consistent environment to work with. As an example, an improperly configured development server could very easily cause software to behave differently than on a properly maintained staging or production platform, or even other development boxes. Who's to blame when the software fails in production? And what happens if the security is compromised on the development server? You should at least have some minimal controls in place.

      Now, that said, I agree with you that developers should be in control of their own application stack on the development servers. I agree that it is completely unacceptable that anyone has to wait two weeks for a Perl module, and that developers should have their own installations to work with. But the underlying operating system, no. Unless they're kernel developers, of course. ;-)

      • I'll also both agree and disagree with you. :) Developers should have the support of admins who do maintain the OS, etc. There should be some standard configuration the admins can restore, and the developers ought to be able to request needed changes (for some apps that might be the OS level, for others it might be as simple as a Perl module or even a config file) and receive those in a timely manner, and all of it ought to be well-controlled and not put into production until it is well-documented and rep

        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers