On Wednesday 14 January 2004 11:15, Chris Albertson wrote: > The way to get this work done is in steps. Some of these > steps will help everyone. This is good as the more people > a step helps the more likely it is to get done. > > 1) First priority. Make a GNU "Autotools" build system for > Asterisk. Thiat is one that uses a ./configure script > There is a patch or "asterisk versin that > does this already. Priority #1 is to get this tested > and into CVS. It is an absolute pain in the but to > support multiple platforms with this. And the work > is already done, except for testing and CVS checkin
It's not going to happen, as it is right now. What is needed is an Asterisk developer, not just a user, who has committed code to the project and is actively involved with its maintenance and development who Mark can trust to stay with the project to maintain the autoconf/automake stuff. Unless this happens (not just a Johnny-come-lately who hasn't contributed a line of code), you're not going to see autoconf/automake in Asterisk. This is the primary stumbling block to autoconf/automake, not any technical reason but purely pragmatics. What this means is, if you haven't contributed any code back to Asterisk and you want to see autoconf/automake, you need to become an active developer of the project before such changes will even be considered. -Tilghman _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
