From: Melvin B. <mel...@eq...> - 2006-07-25 16:40:20
|
As I recall being discussed before when this topic came up, there are apparently some modules, the syslog one comes to mind, which don't play well in at least some environments. I much prefer the validation approach as opposed to the mandatory installation approach. At 12:21 PM 7/25/2006, Micheal Espinola Jr wrote: >Fritz, et all: > >Travis's recent issues with ASSP process hangs were centered around not >having all of the modules installed. Personally, I think the ASSP >process hung while trying to access missing modules, but the specifics >could not be fully determined without more debugging work on Travis's >part. But ultimately the solution was to simply install all the modules. > >As a continuation of a previous discussion regarding having to install >all modules with the ASSP installation - I again put forth the motion >that all modules should be installed and checked for in order for ASSP >to run. If not making a requirement to install all modules, then >perhaps better checks should be in place to prevent subroutines from >being performed if required modules are missing. > >Personally, I think all modules should become a requirement. Any thoughts? > > >------------------------------------------------------------------------- >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 >Ass...@li... >https://lists.sourceforge.net/lists/listinfo/assp-user |