On Tue, 10 Jul 2012 22:44:01 -0300 Wido <wido.gg@...> said:
extra-modules are not part of efl - so not relevant. proto is prototype stuff -
so nothing will happen to it. if its not part of the set of efl we have
releases as 1.x it wont go into the efl tree. ultimately there is a plan to
move to git and this efl tree will be a single git module covering "efl". if
its not there it doesnt go into that module. we'll have a separate git module
for e (if this includes quality apps or not is a question atm - if not we'll
have another git module maybe per good quality app) and then another git module
for "other stuff" which is everything else.
> What about the rest? extra-modules, proto, games, weird stuff? what's going
> to happen to all of them?
> On Monday July 9 2012 23:43:35 Carsten Haitzler escribió:
> > On Mon, 9 Jul 2012 13:28:56 -0300 Wido <wido.gg@...> said:
> > > That means that instead of compiling lib-by-lib in the exact order, we
> > > will just run one (and only one) configure-make-make install ??
> > yes. if u dont want a lib built u'll have to --disable it as opposed to just
> > not download/build it. you will download everything we release in 1 big
> > tarball (or src checkout). deal with it. :)
> > > I like that!!! Is there a reason it wasn't done before?
> > 1. save bandwidth so you only download what u need and want, not everything.
> > 2. make it obvious and easy to people to know they can just use a minimal
> > subset of libs we release to make something so they can have a minimal
> > dependency chain
> > 3. save disk space
> > 4. efl grew organically adding new libs to solve new problems over time. it
> > really didn't start life as EFL - it started as 1, then 2 then 3 libs that
> > happened to come from the same team that solved different problems. it was
> > never envisaged as one big project and toolkit set until much later in its
> > lifetime as it became apparent that is what it had in effect become. this
> > move to a single tree reflects that changed reality in a concrete way and
> > saves us time, effort, and improves many things. it hurts the people who
> > want to download less etc. etc. - but it's a sacrifice worth making.
> > > On Monday July 9 2012 10:15:07 Carsten Haitzler escribió:
> > > > On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen <tom.hacohen@...>
> > > > said:
> > > >
> > > > > On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote:
> > > > > > single configure for all. still producing multiple libs and pc
> > > > > > files, headers etc.
> > > > > >
> > > > >
> > > > > Ah, just a single source tree, got it. :) I thought you were talking
> > > > > about merging the libs entirely.
> > > > >
> > > > > Though, even here we can split core to 2 (base vs graphical)...
> > > >
> > > > nah. not doing that. we are going to have a single src. right now they
> > > > will produce the exact same installed libs/modules/headers/pc files as
> > > > we get now, just a single configure && make && make install.
> > > >
> > > >
> 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-users mailing list
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@...