On Fri, Feb 24, 2012 at 12:38 PM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Fri, 24 Feb 2012 12:26:42 +0100 Vincent Torri <vincent.to...@gmail.com> > said: >> Hey >> >> i'm against the merge of exotic just one week before the release. >> >> Currently, there are a lot of copy/paste errorrs in the autotools, as >> well as some stuff that could be done a lot better. >> >> Cedric : let exotic in svn, but please revert all your changes in the other >> EFL. >> > > i'm with you there - postpone until after release.
I obviously disagree for three reasons : - It doesn't impact non user of Exotic, so it's irrelevant for most people. - EFL 1.2 is likely to be the latest version that you can port with thread support and pipe. This will likely raise the complexity of porting it. So my understanding is that 1.2 is the latest easily portable version of the EFL. - There is no new API in Exotic, it's just renamed system call. So we already know that the API should never change. For all this reason, I think Exotic inclusion in the EFL should be there. -- Cedric BAIL ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
