On 17/12/2012 13:52, Johan Vromans wrote:
Lyle <webmas...@cosmicperl.com> writes:
Michael is right. I deal with setting up Perl driven software are a
wide variety of systems. This often means setting up Perl itself
because the system doesn't have one, or to have a non system instance.
It can be a real pain, it shouldn't be, it should be easy and straight
forward for all. TIMTOWTDI, relying on the OS for package management
can be far from idea, or not even an option.
I think it is neccesary to make a distinction between developers, power
users, and desktop/end users. Developers and power users usually know
how to deal with CPAN/local installs and package management. 'Command
line' and 'root' do not have real secrets for them.
True, but even for power users managing Perl modules and dependencies
can feel needlessly long winded, and not uncommonly fraught with
complications. Clashes between versions, system packages, cpan installed
modules, missing deps, etc.
When one can spend what feels like an eternity installing deps for a
Catalyst app, knowing full well that things like Drupal can be installed
in minutes, doesn't do the image of Perl an favours.
Desktop users, on the other hand, just use point and click on desktops
and web sites, and things like 'Perl' and 'modules' do not mean anything
significant. For these users, an application is just a single piece of
software that gets installed with the click of a button. If it is a Perl
application, this means you have to provide Perl and all necessary
libraries and modules with the install kit[1]. Installable packages can
be created with PAR, althoug personally I prefer Cava Packager
(especially in combination with Citrus Perl). Other people may wish to
use PerlApp.
-- Johan
[1] Unless you create installers for each and every specific platform
the customers use -- which is a huge maintenance burden.
I started a design a project I called PerlSI a few of years back (Perl
Scriptable Installer), which aimed to remedy this among other things.
Unfortunately I started a part time degree and didn't get far with it.
Maybe next year I'll have chance to look at it again.
Lyle
