|P is for Practical|
perl application installationby arcnon (Monk)
|on Feb 11, 2006 at 16:38 UTC||Need Help??|
arcnon has asked for the
wisdom of the Perl Monks concerning the following question:
I could really use some direction folks.
I wrote a application. And it came from on high that it is so great that it would be used at several other campuses yeah!!!!.... Unforunately it hasn't been as easy to make happen as I had hoped.
It seems that because of the asp.net crazy that the other campuses are perl illerate maybe resistant is a better word.
So the politics run red in the IT department. It has been deemed that it isn't my responsiblity to go to the differant campuses and set them up BUT I have to support them besides the normal bugs and what not.
the application has a web interface that generates data entry forms with custom widgets and manages mutiple instances of the application and queries of the form data. Much of the work is done through a deamon that generates a custom CGI::Application for use with the custom widgets and queries.
I was thinking if I could create a installer it would be ideal and take most of the headache from the process. But after googling for some type of solution I am still drawing a blank. Should create it as a 'bundle' or some hand woven installer?
I realize that I have a few hurdles left... windows vs linux installations, Line endings, install locations, module dependancies and whatever crops up as I proceed. If I don't use a 'bundled' installer.
Is creating a 'module bundle' the best approach for this or is there some magic that I don't know about.