On Sat, 21 Dec 2013 09:57:23 +0900 Cedric BAIL <moa.blueb...@gmail.com> wrote:
> Cedric Bail > On Dec 21, 2013 12:54 AM, "Mike Blumenkrantz" < > michael.blumenkra...@gmail.com> wrote: > > > > discomfitor pushed a commit to branch enlightenment-0.18. > > > > > http://git.enlightenment.org/core/enlightenment.git/commit/?id=5a6dcf17f322c52cf9745e6f83d9c11a6763f55c > > > > commit 5a6dcf17f322c52cf9745e6f83d9c11a6763f55c > > Author: Mike Blumenkrantz <zm...@samsung.com> > > Date: Fri Dec 20 10:50:40 2013 -0500 > > > > add separate elm version requirement > > > > elm versioning for stable series will be different than efl > versioning, so these are not the same. > > > > also now that the theme for enlightenment is distributed with > elementary, there may be (and is) a MAXIMUM usable version of elementary > which will work with a given E version while I work to stabilize various > api across the releases. as a result, e18 RELEASES will not be usable with > elm >= 1.9 (current git and beyond). > > Hum, why? We're supposed to have a stable abi for theme also. I may be not > involved enough with the development of elementary, but this decision feel > strange to me and is likely to displease distribution, so care to explain? just because the enlightenment edje theme got shoved into elementary doesn't mean its api is stable. it's pretty obvious reading it that there was little forethought or set direction and that it just evolved organically however people felt that it should at the time. as a result, it's a giant mess which needs to change. E18 broke theme compatibility with E17. this wasn't "as much" of an issue since the theme was distributed with the app. now that the theme is all distributed with elementary (a decision which, despite the memory savings, I still disagree with because of the exact reason raised here, though I also have no good solution for aside form having yet another required package which is just the combined theme), this means that a library release will contain api breaks in the theme for the as-yet unreleased app, which means that the app will then be incompatible with newer versions of the library. it's a chicken-and-egg problem without a good solution. given that "this is the way we're doing things", I'm choosing to not be held responsible for maintaining compatibility with previous versions for an indeterminate period of time into the future for an api which has NEVER been considered stable, just as the eo api has been released without needing to retain compatibility. > > > tl;dr: don't mix live versions with releases. > > --- > > configure.ac | 9 +++++++-- > > 1 file changed, 7 insertions(+), 2 deletions(-) > > > > diff --git a/configure.ac b/configure.ac > > index 900d3fb..b4f86fe 100644 > > --- a/configure.ac > > +++ b/configure.ac > > @@ -96,6 +96,9 @@ AC_DEFINE(HAVE_ENVIRON, 1, [Have environ var]) > > efl_version="1.8.3" > > AC_SUBST(efl_version) > > > > +elm_version="1.8.2" > > +AC_SUBST(elm_version) > > + > > AC_CHECK_HEADERS([sys/timerfd.h sys/ptrace.h arpa/inet.h netinet/in.h]) > > > > dnl AC_CHECK_HEADERS(X11/extensions/shape.h,, AC_MSG_ERROR([Cannot find > X11/extensions/shape.h. Make sure your CFLAGS environment variable contains > include lines for the location of this file])) > > @@ -552,7 +555,8 @@ PKG_CHECK_MODULES(E, [ > > eina >= ${efl_version} > > eldbus >= ${efl_version} > > eio >= ${efl_version} > > - elementary >= ${efl_version} > > + elementary >= ${elm_version} > > + elementary < 1.8.99 > > emotion >= ${efl_version} > > $eeze_mount > > $udisks_mount > > @@ -574,7 +578,8 @@ efreet-trash >= ${efl_version} \ > > eina >= ${efl_version} \ > > eldbus >= ${efl_version} \ > > eio >= ${efl_version} \ > > -elementary >= ${efl_version} \ > > +elementary >= ${elm_version} \ > > +elementary < 1.8.99 \ > > emotion >= ${efl_version} \ > > $udisks_mount \ > > $eeze_mount \ > > > > -- > > > > ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
