On Fri, Jan 18, 2013 at 1:11 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > over the past 16+ years i've learned that: > > 1. autotools likes to upgrade regularly from 1.xx to 1.yy and so on > 2. as it upgrades it often creates brekages, deprecates stuff and breaks it > etc. > 3. you often can't just choose any combination of versions of automake + > autoconf + libtool + gettext etc. - you need a "magic working combo" > 4. reality is that "we make it work for us". until "us" is the most number of > devs. what the above magic combos are changes over time, and then a year goes > by and it's all good and then suddenly some distro revs, upgrades these tools > and everyone is bitching that things don't build anymore because they upgrade > within days or weeks of the new distro release. > > re-running autotools is something DEVS do. our job is to produce tarballs that > dont need to run autotools. so it must work for us. we work on the code every > day and produce such tarballs. reality is we CANNOT make it work for everyone. > well not from the "run autotools" point. our job is to make TARBALLS that work > for everyone.
I sense quite a lot of pain in that mail... I also seem to have failed to show/realize/convey that we pretty much say the same thing in other words. -- Regards, Alex-P. Natsios (a.k.a Drakevr) ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
