TreeWalk wrote: > Uhm .. wait a minute.. why carrying all the perl modules with ASSP > when the modules may be updated (e.g. bugfixes etc..) ? I think it > may be a good idea to setup a cmdline perl script sitting inside > the ASSP folder; at that point to setup ASSP one would just need > to install a working perl, extract the ASSP files into whatever suitable > folder and run the "setup.pl" script; the script in turn will proceed to > download and install all the needed bits and pieces (perl modules) > create the required folders (if not already there) and so on; I think this > may be a good idea; especially since the same script may then be > used for multiplatform setups *and* since it may be called from any > "automated installation tool" :)
I also remember years ago when this was discussed that a lot of people complained that they did not want to be forced to install specific versions or trample-over existing (but perhaps not current) versions of installed modules used with other applications. The same issues and reasons why module functions are kept separate from the code, and not fully integrated into ASSP. Personally, I like the idea of a small installation footprint for ASSP, downloading prerequisites separately, scripted or otherwise. Although I am usually a fan of bundling - I have reservations about it being done with ASSP. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
