On Fri, Feb 24, 2012 at 4:29 PM, Cedric BAIL <[email protected]> wrote: > On Fri, Feb 24, 2012 at 4:14 PM, Vincent Torri <[email protected]> > wrote: >> On Fri, Feb 24, 2012 at 3:29 PM, Vincent Torri <[email protected]> >> wrote: >>> On Fri, Feb 24, 2012 at 3:24 PM, Cedric BAIL <[email protected]> wrote: >>>> On Fri, Feb 24, 2012 at 3:13 PM, Vincent Torri <[email protected]> >>>> wrote: >>>>> On Fri, Feb 24, 2012 at 3:09 PM, Cedric BAIL <[email protected]> wrote: >>>>>> On Fri, Feb 24, 2012 at 3:01 PM, Vincent Torri <[email protected]> >>>>>> wrote: >>>>>>> On Fri, Feb 24, 2012 at 2:57 PM, Cedric BAIL <[email protected]> >>>>>>> wrote: >>>>>>>> On Fri, Feb 24, 2012 at 2:38 PM, Vincent Torri >>>>>>>> <[email protected]> wrote: >>>>>>>>> On Fri, Feb 24, 2012 at 2:32 PM, Cedric BAIL <[email protected]> >>>>>>>>> wrote: >>>>>>>>>> On Fri, Feb 24, 2012 at 2:08 PM, Vincent Torri >>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>> On Fri, Feb 24, 2012 at 2:02 PM, Cedric BAIL <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>>> On Fri, Feb 24, 2012 at 12:38 PM, Carsten Haitzler >>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>> On Fri, 24 Feb 2012 12:26:42 +0100 Vincent Torri >>>>>>>>>>>>> <[email protected]> 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... >>>>>>>> >>>>>>>> static compilation is working. I am running it every day since 2 >>>>>>>> months with this patch set. I am able to build statically up to >>>>>>>> elementary with all eina and evas module statically build also. Could >>>>>>>> you elaborate why you think the static build is broken ? >>>>>>> >>>>>>> look at all the requirements_*** that are almost all wrong >>>>>> >>>>>> Was all this thread about this copy & paste error ? If yes, then that's >>>>>> solved. >>>>> >>>>> there are other problems in the autotools >>>>> >>>>> and no, it's not only copy/paste error... Fuck don't you read what i >>>>> wrote ? >>>> >>>> You are not writing meaningful information. I am here trying to >>>> decipher what you write and you are not helping at all. Your mail is >>>> like a riddle, there is no clear pointer at the error. Sorry I can't >>>> read your mind from where I am. >>>> >>> >>> it seems you didn't read that : >>> >>> I prefer say it again : I'm not against exotic as a library. I'm >>> against merging it in the EFL just before the release. Note that we >>> already did that before (not adding features just before a release). >>> Here, it's not merging something one month or 2 before a release. It's >>> only 1 week before it. >>> >>> So we have HIGH probabilities to release something broken (as not >>> being tested a lot by others like you). And as you break often >>> stuff... >>> >>> And for what ? An obscure OS. >>> >>> So it seems that you don't care about the robustness of the future release. >> >> so you don't want to remove your exotic merge ? > > Sorry I was expecting technical argument and you pointing to technical > issue that I could solve, but that's not the case.
ok, i quickly looked at your patches (around 5s for all of them) and i spotted 2 problems. It seems that you even don't want to thank me for 1) looking at your patches 2) spotting bugs. but I'm ok with that. > To make it short > your point is just: "cedric should not commit code in the week before > a release". no. You are *heavily* modify the autotools. The errors also there can be subtle. > You know I can bork svn in more subtle way that would take > it more than one week to get detected ? Seriously my change in > Ecore_Thread are likely much more complex and risky, than this commit > for enabling Exotic. But you didn't even raise your hand on it. no comment... > As to the point, it's not a library to support one obscur OS, but make > it possible to support all obscur OS. It's not like evil or escape, > that target one system and require us to change every library when we > want to support another OS. And this make it possible for the 1.2 > branch to be the easy to port branch. > > If there is nothing fixable in time. I mean hard point, that really > break build, then yes, I am ok to revert. But right now, I have > adressed all the typos that were detected and all the buildbot seems > to be happy at the moment. I am still waiting for your technical > point, when you are done with your rants of course. my rants ? You are committing unknown stuff, without telling people. Your argument is : after 1.2 it will be harder, so let's get it in just before a release. Great. 2 other people disagree : raster and me. But you don't care. So now, if there is a big problem with your merge (i don't know, and actually, i care about that less and less), we will have a good publicity. your behavior is a rant. Vincent ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
