On Tue, Jul 10, 2012 at 11:43 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Mon, 9 Jul 2012 13:28:56 -0300 Wido <wido...@gmail.com> 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
Even with the one big tree, can we use a minimal subset of libs? Not everyone wants to use every libraries in efl and as far as I know that's one of the pros of efl. Daniel Juyung Seo (SeoZ) > 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.haco...@samsung.com> >> > 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. >> > >> > >> -- >> >> -- >> Wido > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > ------------------------------------------------------------------------------ > 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 > enlightenment-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ 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 enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
