[Asterisk-Dev] Dev call 1.2 release discussion

[Luigi Rizzo]

On Fri, May 06, 2005 at 04:08:22PM -0400, Jerris, Michael MI wrote:
>  
> > Jeremy McNamara
> > 
> > Autoconf is not the answer.   I have a make menuconfig addition I am 
> > working on.   I have mimicked the basic concept of the Linux kernel's 
> > menuconfig option.
> 
> Autoconf is not the answer to what?  Autotools are potentially the
> answer to many of the crossplatform issues we have had lately, and

well well well... this is going to be a religion war.

autotools introduce a different (additional) set of dependencies
in the build system.

I may accept that auto* config files written by someone who is
competent and fluent in the use of these tools may
solve problems; HOWEVER, there are not so many competent
autotools programmers, and in many cases the config files are just
copied from other programs (bugs included) and hacked by
trial and error until they do something acceptable on the one
system they tried them on.

Which in the long term means having unmaintainable build
systems, and one that you have no control over once the 'guru'
who write them stops taking care of them.

Because the build system evolves a lot over time, i consider
this a high risk.

	cheers
	luigi

> before you ask if I will support it for the next 100 years, there have
> been several people who have said they are wanting this AND ready to
> support it.  A make menuconfig would also be worth a good look as well,
> thanks.
> 
> Mike
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev