On Fri, Feb 24, 2012 at 2:32 PM, Cedric BAIL <cedric.b...@free.fr> wrote: > On Fri, Feb 24, 2012 at 2:08 PM, Vincent Torri <vincent.to...@gmail.com> > wrote: >> On Fri, Feb 24, 2012 at 2:02 PM, Cedric BAIL <cedric.b...@free.fr> wrote: >>> 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 : >> >> ii relevant because > > Expected from you :-) I know that you have a so strong mind and will, > that you will not accept anything easily. > >>> - It doesn't impact non user of Exotic, so it's irrelevant for most people. >> >> the are errors in the autotools. Just before the release... I won't >> have tiime to fix them as i'll be away during more than a week > > Please point them, that would help get them fixed. Or just wait a few > hour that Gustavo wakeup and say that with CMake, it would have been > eathier ;-)
some variables like _LIBS and so on, some requirement variables (you just broke static compilation...) etc... > >>> - 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. >> >> And having exotic in 1.2.1 is possible. > > That's adding a new feature. Doesn't match like a bug fixes or > maintenance. That would mean that 1.2 become a maintained fork of the > EFL. I don't like that much this idea. > >>> - There is no new API in Exotic, it's just renamed system call. So we >>> already know that the API should never change. >> >> not a good reason... > > I like that argument. > >>> For all this reason, I think Exotic inclusion in the EFL should be there. >> >> so, no strong reason at all. >> >> You're adding quickly something that has not been tested. That should >> merge evil and escape, and actually, nothing was merged. Can be post >> poned. > > You maybe missed it, but this library already support another OS, i know it supports Coyote (or at least, it's a strong guess) > that both escape and evil doesn't support. of course they don't support it ! > It's proven and work. where's the proof ? Currently, you have broken static linking... Vincent > It provide > all the grunt work for people that want to port EFL to any strange OS. > So people that want to make it run on "embedded" OS or custom OS can > now do it very easily with EFL. > -- > 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 ------------------------------------------------------------------------------ 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
