Apparently, though unproven, at 14:28 on Wednesday 09 February 2011, P Purkayastha did opine thusly:
> >> dont use ANY --enable/disable configure flags. defaults are what you > >> want. using any such flags you do at your own risk. > > > > That breaks Gentoo in all sorts of horrible ways. > > Strange. My broken e17 + gentoo is somehow chugging along for a good 4th > year now ;) > /me starts looking for the broken pieces ... I don't mean it breaks Gentoo such that bits of EFL lie all over the floor right away. Gentoo, by design, lets the user control what features are installed and what is not installed via USE flags. This sets up dependencies. When a build script on Gentoo relies on automagic enabling of features, only stuff that is already present is used. This is NOT up to some distro packager, it is up to the user. There is no method to set up optional dependencies so the usual route is to DEPEND on nothing and rely on magic (or user vigilance) or DEPEND on everything which makes the average Gentoo user freak out. emerge --depclean is then useless at helping remove unneeded deps later on. But you know all this already right? Developers can by all means use automagic deps; I'm opposed to the practice myself but I can't stop devs doing it. But also provide explicit --enable/-- disable options in ./configure for source based distros. -- alan dot mckinnon at gmail dot com ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
