>From my limited understanding of EDE, it is a set of automated scripts that attempt to set a the complete set on development environment setting for a very select set of operating systems: CentOS 5 and Fedora 10.
The autoconf framework is not the greatest gift to mankind, but in many ways it acts as a way to detect configuration deficiencies and present them to the user with some direction on how to correct their system. Together with proper documentation on the wiki, this allows everyone under a variety of environments and operating systems a fighting chance to setup their system. Today, someone on SuSe needs to read thru script scripts and see what applies and doesn't. I feel many more people can update documentation with instructions for a particular OS, but not a lot of people can update shell scripts, or if they can, are willing to go thru the effort of contributing those changes back. Lastly, I fear that the EDE scripts will be used for a catch-all for inflexible environment settings. For example, I discovered Openfire would not send IM messages when someone didn't have a static IP route configured in their hosts file. IM messages were trying to be delivered to [email protected]. This particular issue is probably best suited for the config check of the openfire startup script, not autoconf, but my point is more that it shouldn't be in EDE. The last lastly, scripts that need to run as root that do all sorts of magic to my OS are a distant second to documentation that tell me to these set of more familiar instructions. No disrespect to contributors of EDE, setting up a system is a PITA and sharing your scripts to do so is being generous. Thoughts? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
