On Fri, 2008-08-22 at 10:25 -0400, hymie! wrote: > Why can't ./configure just assume that if I'm missing some of these things, > I don't want them (like it used to)?
Because requiring users explicitly override dependencies ensures that we are dealing with a known set of functionality in the majority of cases - and in other cases the user will know they did something "different". If you know you have all the dependencies you need, and don't want to manually disable them individually, the old behavior can be replicated using: ./configure --disable-missing-dependencies Regards, Stu. _______________________________________________ Support mailing list [email protected] http://pidgin.im/cgi-bin/mailman/listinfo/support
