|XP is just a number|
Perl application packagingby bibliophile (Parson)
|on Jan 26, 2005 at 16:48 UTC||Need Help??|
bibliophile has asked for the
wisdom of the Perl Monks concerning the following question:
I've been happily hacking away on a collection of modules that implement various bits and pieces of an application (eg: a database abstraction module, a data abstraction module, a handful of standalone utility scripts (and the modules they depend on), and a whack of Perl/Tk widgets), each with it's own test suite, etc.... plus of course the app script itself.
I'm getting to the point where I'd like to be able to install the whole collection in one fell swoop.
I've been looking at things like creating Bundles (from the CPAN FAQ) and/or PAR, though I'm not sure this is the correct way to go - this is new territory for me.
So the question(s): How do you handle building/distributing Perl applications? How about module build-order dependencies (eg: app::DB needs to be built after app::DB::PostgreSQL (or app::DB::MySQL, depending on what the user has installed))?
I'm not looking for hand-holding here... just a nudge in the right direction :-)