On Thu, Aug 30, 2012 at 8:31 PM, Gustavo Sverzut Barbieri <[email protected]> wrote: > On Thu, Aug 30, 2012 at 12:13 PM, Dennis.Yxun <[email protected]> wrote: > >> On Thu, Aug 23, 2012 at 8:21 AM, Carsten Haitzler <[email protected]> >> wrote: >> > On Wed, 22 Aug 2012 12:12:10 -0300 Leandro Dorileo < >> [email protected]> >> > said: >> > >> >> On Wed, Aug 22, 2012 at 11:18:30AM +0900, Carsten Haitzler wrote: >> >> > On Wed, 22 Aug 2012 12:10:22 +1000 David Seikel <[email protected]> >> said: >> >> > >> >> > > On Wed, 22 Aug 2012 10:20:41 +0900 Cedric BAIL <[email protected] >> > >> >> > > wrote: >> >> > > >> >> > > > so as soon as Evas and Ecore get merged inside the new unified EFL >> >> > > > tree in a few weeks, >> >> > > >> >> > > I think this is the first time the timing of the merge has been >> >> > > mentioned in the mailing list? It's all going to happen in a few >> >> > > weeks, the big EFL tree merge, a move to git, release of e17, the >> next >> >> > > sequel to Duke Nukem - Duke freezes hell? >> >> > > >> >> > > Enquiring minds wish to be enlightened. >> >> > >> >> > after this 1.7 release we have 3 major things to do: >> >> > >> >> > 1. commit and stabilize patches that are pending due to release >> freeze. >> >> > 2. merge into single efl tree >> >> >> >> >> >> The merge into a single efl tree will also involve the move from svn to >> git? >> >> /me just wondering. :) >> > >> >> hey, raster, I have one question about the single efl tree >> does this simply pull all the source together? or also merge the build >> system? >> (I haven't dive too deep to check the history information) >> >> I'm coming from Gentoo Linux, and my question is, >> if we merge all the build system together, then must I >> download/extract *all* the source code to build one library?? >> Could I still have the previous way to download/extract one specific >> library and only build then, I mean, I'd like to build each of them >> separately. That probably would make my life much easy. >> >> merge all the source code isn't the problem, but I wish it could build >> separately.. >> hopes I make my words clearly, thanks >> >> > there will not be any more build one single library by default. You'd have > to hack the code and change it yourself. This is on purpose. > > You'll have to replace every package with a single "efl" package.
i can add easily an option to build the requested packages with their dependencies vincent ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
