On Tue, Dec 4, 2012 at 10:17 AM, Gustavo Sverzut Barbieri <barbi...@profusion.mobi> wrote: > David, > > Your case is extreme and really an onus we shouldn't take. You can maintain a > patch set or run 1.7.
I don't think that he is a corner case. As EFL has been designed first for embedded many developers use it in a constrained environment. My understanding of this cut out configure option is to first trim them down as much as we can and then add later the one our developers need. So basically if he say he doesn't want Ecore_Con for whatever reason and this become a hard dependency in Ecore_Evas (current state of affair). Then, we should accept a patch that add --disable-network and would just disable all internal code of Ecore_Con by a dummy stub. The rest of EFL will still think that Ecore_Con is there, it will just always fail to connect or listen to anything. That's just an example of where I think we should be going. We don't have a terrificly big users and developers base, so we should not follow the path of removing feature for the sake of it, like some religious from another project do. -- Cedric BAIL ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
