Andres said:
You could ship your web application with Perl and Apache binaries
already configured to work with your web app. You will save a lot of
time during the installation because it will be just unpacking a tar
file. This can be more complicated if you have to support a lot of
OS's. But it's an option.
There's one software package I was looking at that is basically a
website that interfaces with MySQL via PHP. One vendor wants to come
to your location to do the complex installation and another one sells
it already set up on a hard drive.
If you ship it with with Perl and Apache binaries already configured,
what if you mess up what people are already running? If your
application will be the only one running, why not bundle the whole
configured OS in an image file?
I have had the same problem with Perl modules. What if you don't have
access to the internet during setup? What if you ship with all of the
modules needed, but you were not aware of some dependencies on other
modules that are not standard?
Recently, I used Switch.pm just to be cool and I had trouble moving the
script to a machine without internet access because Switch.pm depends
on some other modules I didn't save to disk. I just went back to if,
elsif... I guess avoiding non-standard modules unless absolutely
necessary improves portability.
***Why not make cpan modules available as a DVD image? Project
Gutenburg does it with their files. You won't always get the newest
stuff, but at least you get all of the important stuff. Or for profit,
somebody could sell subscriptions to up to date DVDs.
2005-02-22 online since 1995-10-26
2784 MB 271 mirrors
4187 authors 7662 modules
wana