On Tue, 27 May 2014 16:36:47 +0200 Guillaume Friloux <[email protected]> said:
hey man. calm down. you are trying to catch up on 2 years of development in one bang. yes it's painful. also note that the majority of people packaging/using efl need and WANT the gui. EFL was written FOR the purposes of building a window manager. it was split out from the wm binary because "hey some of these libs may be useful to other people", but the focus of EFL is gui. you CAN get what you want. build with everything - it only take like 2-5 minutes on a vaguely decent machine (including configure), and then: make DESTDIR=/tmp/myefl then delete the stuff in /tmp/myefl you don't want - and tar/package up that dir to distribute to your boxes. you only need the dependencies on your build box - not on all of the targets. this is why it wasn't considered a priority to have a special build profile like this as it can be done post-build. this is actually how most distributions build and package things - they build it all then split it up. you should give it a go. as for 1.7 maintenance - do you really think we have the manpower to do both development and move efl forward with the insane list of requests for features and other stuff, as well as maintain efl 1.1, 1.2, 1.7, 1.8, 1.9 AND 1.10? we don't even have branches for 1.7 and below in efl (elm has 1.7 and 1.0, but not efl)? have you send the patch review queue? it eternally gets bigger - we try and keep up. bugs - they don't go down, only up. take a look at wishlist priority bugs one day to truly see the backlog. do you think we have the luxury to support old versions of efl for years? we don't. i''m really sorry that this causes you to make some choices - package as above, which i assume you'll just reject out of principle, even if it perfectly does the job, simply with a bigger set of deps and maybe 1-2 mins of extra build time on just the build box, or spend some time and effort doing the work needed to support you - either stay on 1.7 and do your own long term support, or to do what YOU need to make current efl work better for you. scratch your own itch. you should calm down man. take it easy. there isn't some conspiracy to piss you off - in fact the efl tree merge has been nothing but positive responses from everyone EXCEPT you. packagers love it. we have fewer problems of efl builds that are poorly configured and missing features. individuals who track efl from git or tarballs have an easier time building and keeping up. doing the tree merge was a massive effort and took quite a while and having ultimate configurability wasn't something we can keep. in fact it's discouraged to stop there being broken efl builds. configure.ac is complicated because we still have a fair number of build options to support multilpe os's, older distributions missing dependencies etc. - if we forced everything as a dependency you'd complain too as now you would have precisely zero choice, and we'd lose support for bsd's, osx, windows, and distributions except the latest and greatest on the bleeding edge. you need to stand back and realize that efl is complex by its nature. this is an artifact of history. thus its build is complex. one day (efl 2) things will simplify and we'll merge libraries and thus reduce inter-dependencies, thus reducing build complexity (and code as well), but that's a slow march to that goal and there are other higher priorities until then. we can't do everything at once when everyone would like it. so calm down man. chill. stand back and see the forest from the trees. :) > Congratulations, e devs, you won at ruining my work. > > Since 1.5 years, i am stuck with 1.7 branch due to your crazy ideas. > Your first step as been to make me unable to disable the building of libs i > dont need, when merging tree (ALL of the GUI libs). > > Then, some of you told me to make a 'server' profile, which is stupid because > it is incompatible with building with the dev profile, for exemple. > > What happenned next is that decision to only add security fixes to 1.7 > branch, no fixes at all. Bam! > > Luckilly, i was really busy, and then having my enterprise shutting down, so > i had no time to look at the madness. Since over 6 months, a bigger > enterprise bought us, and since yesterday, ive find some time to work on > migration to EFL 1.10. > > Needless to debate about how this configure.ac file is stupidly huge, and far > from KISS principles. After almost a day looking at how things are now built, > i started writting the server profile. It wasnt pretty (Oh yeah, really not > pretty), but it was working, until i removed ecore_evas et and ecore_imf. > What the fuck is wrong with you guys ? I cant even build the doc because some > guy thought it would be cool to have a C tool automagically generating text > previews, using ecore_evas! > > How far are you going in your ideas ? > I have been completely put apart from EFL, with everyone ignoring my work, my > needs. > > So i have understood, everything in EFL starting with a number of 1.8 or > upper is ONLY dedicated for GUI stuff. No one is supposed to use > eina/eio/eet/ecore separately. Even if i ended my work with server profile, i > know there will always be people to either remove or break it (You removed it > once, you can remove it always). As you seem to be able to break anything the > day you want, ignoring 'others', i better stop. > > I get it. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
