Le 21/02/2014 01:59, Carsten Haitzler (The Rasterman) a écrit : > On Thu, 20 Feb 2014 19:49:52 -0500 Christopher Barry > <[email protected]> said: > >> On Fri, 21 Feb 2014 09:04:48 +0900 >> Carsten Haitzler (The Rasterman) <[email protected]> wrote: >> >>> On Thu, 20 Feb 2014 22:53:13 +0100 Pierre Couderc <[email protected]> >>> said: >>> >>> modules are patches against e. they need to update as e updates. yes - >>> e from git has no more e_container.h. :) those that want those modules >>> to work.. need to update them. :) >>> >> Maybe a dumb question, but if adding a new module requires a patch to >> e, then why/how is that modular? :) > no. modules *ARE* patches. they don't need patches. they *ARE* patches. > patches > need to be updated relative to the code they depend on. we don't maintain a > stable api/abi within enlightenment - it's not a library like the efl libs are > with a stable api/abi for development. e's internal api/abi moves and changes. > modules have to adapt to keep working like any patch does. > > OK, I conclude that I am too "young" in Enlightenment to try the git version, and I come back to a stable version...
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
