On Wed, Feb 10, 2016 at 2:54 AM, Tom Hacohen <t...@osg.samsung.com> wrote: > On 12/01/16 00:42, Cedric BAIL wrote: >> As we are moving forward with a stable API for binding, one of the >> main "weirdness" that is still exposed is that you need to actually >> require two differents library to use efl. Also the only reason why we >> haven't merged elementary so far as been because it still depend on >> webkit-efl and webkit-efl depend on elementary. >> >> I am going to address that during next efl release cycle, by moving >> the webkit dependency to be a module (like evas_generic_loaders and >> emotion_generic_loaders). Once that is done it will be technically >> possible to merge the both of them. >> >> This open a question, does anyone see any other reason to not merge >> elementary ? >> >> If there is no other problem being seen to do this, there is a few >> things that will be impacted : >> - elementary developers branch can not be merged into an efl branch >> automatically. Developers will have to either finish their patch >> before we merge or have to take care themself of doing the move from >> an elementary branch to an efl branch. >> >> - for the same reason, phab patch on elementary that won't have landed >> before the merge will also be abandonned and their respective author >> will have to move their patch on top of efl new merged tree. >> >> Due to the above effect, we should come with a clear timeline if and >> when we do that merge to allow everyone to handle that big of a change >> early enough to not loose time on patching the wrong piece of code. >> Also I think this is going to impact efl 1.18 release cycle, and maybe >> it should be adapted with maybe a technology preview in the middle of >> the release cycle just after the merge ? >> >> Stefan what is your take on such a big change ? > > While preparing for the merge, I came up with another very serious > reservation I have: build time. > > At the moment it's very annoying to build just parts of the efl. > Changing a header in Eo/Eina will trigger a full rebuild of everything. > That is extremely annoying, and will be even worse once elementary is > in. I think we need to fix that first.
Yes, that's part of my planned work on autotools as I will need to work on it during the elementary merge. > Unrelated: have you moved the webkit dependency out yet? Not yet, this is my job from today and the next week. Cedric ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel