On Saturday, 01 December 2007, at 10:39:49 (+0100), Vincent Torri wrote: > Albin Tonnerre (aka Lutin) requested configure scripts to fail when > an option is requested with --enable-*, but the dependancies are not > met. > > Albin wrote a patch for that behavior. It's attached. > > basically, it replaces want_foo="yes" by want_foo="auto" when needed > and check if that variable is changed or not when --enable-foo is > passed to configure. if --enable-strict is passed to configure, the > dependancy is not met and want_foo == yes, then AC_MSG_ERROR is > called.
Albin and I discussed it when he first posted it. When I read it through the first time, I thought it would break certain things. Turns out I had just misread the patch. It looks fine to me. The default behavior is still the same (auto-detect), which is really the most important part, IMHO. I'd say go for it. If anyone had a strong objection, they've had several days (since Albin's original post) to voice them. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "But I dumped her. My motto is, 'Get out before they go down.'" "That is so *not* my motto." -- Monica Geller and Joey Tribbiani, "Friends" ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
