12:19: apt-get install enlightenment

In order to build libframeworkd-phonegui-efl, I need a native copy of edje_cc. It looks like Debian's starting to bring the whole EFL suite in, but at least some parts (include edje) are still restrained to the experimental distribution. All of the binaries in experimental' are, of course, build against theexperimentalversions of their requisite libraries, which means that the binary packages are *dependent* on experimental library-packages..., which would seem to mean that I basically have to upgrade an arbitrarily-wide swath of my otherwise-perfectly-finelennybox toexperimental--pulling inexperimentalversions of glibc, GTK+, GLib, and maybe even a few *applications* that can run only with the same version of a library as the one with which it was built..., and then upgrading more libraries to satisfy those applications... recursively until it all works out... And maybe it'll continue to \work out' after that, or maybe it won't--maybe something will break at some point and require time-consuming manual intervention.

The thing is, stable (lenny) and experimental are, by definition, not a single cohesive mass--they're two independent universes, and aren't really (really aren't) guaranteed to match up at all with each other in the long run. In other words, there's a reason why experimental is called "experimental". All bets are off.

Well, apt-build to the rescue. apt-build helps us get a source-package from one distribution, rebuild it against our own distribution (thusly replacing the foreign happenstance-dependencies with native happenstance-dependencies), and install it without having to upgrade arbitrarily-wide swaths.

Because, when installing from source, all we need is source-level compatibility, which is a lot easier to get than binary-level compatibility. Open Source FTW.

Actually, since I need to build and install several layers (edje -> evas -> embryo -> ecore ...) of library-packages, maybe I should be looking at srcinst....

[Reply]