Is there a Standard or Best Practice for Perl Programs, as opposed to Perl Modules?

Posted by swestrup on Stack Overflow See other posts from Stack Overflow or by swestrup
Published on 2010-06-07T00:03:44Z Indexed on 2010/06/07 2:42 UTC
Read the original article Hit count: 415

I've written any number of perl modules in the past, and more than a few stand-alone perl programs, but I've never released a multi-file perl program into the wild before.

I have a perl program that is almost at the beta stage and is going to be released open source. It requires a number of data files, as well as some external perl modules -- some I've written myself, and some from CPAN -- that I'll have to bundle with it so as to ensure that someone can just download my program and install it without worrying about hunting for obscure modules.

So, it sounds to me like I need to write an installer to copy all the files to standard locations so that a user can easily install everything. The trouble is, I have no idea what the standard practice would be for this. I have found lots of tutorials on perl module standards, but none on perl program standards.

Does anyone have any pointers to standard paths, installation proceedures, etc, for perl programs? This is going to be complicated by the fact that the program is multi-platform. I've been testing it in Linux, but its designed to work equally well in Windows.

© Stack Overflow or respective owner

Related posts about best-practices

Related posts about perl