tracking down the dependency problems..

Hi,

just fyi so you know whats going on:

I'm right now doing a reference build with 'abort when a package build
fails' turned on. That way I can debug all the remaining dependency
problems (wrong build order).

When this is done, I'll remove all the entries from scripts/dep_fixes.txt,
use our by then correct build order to aut-detect which dependencies are
bogus ones and fix them.

Then I will make a test build with the cluster-build dependency order
(build packages as early as possible, according to their explicit
dependency information) in order to find missing dependencies..

I hope to get the first step (build which is running right now) done during
the linuxtag in kalrsuhe this week. (I just need to regulary check if the
build is still fine and make a small dep fix whenever something goes
wrong - that should be doable while beeing at the rock booth at linuxtag.)

yours,
 - clifford

-- 
Optimization is easy:
39. Make it right before you make it faster.
43. Let the compiler do the simple optimizations.
46. Keep it simple to make it faster.
47. Don't diddle code to make it faster - find a better algorithm.
48. Instrument your programs. Measure before making "efficiency" changes.
-- from "The Elements of Programming Style" by Kernigham and Plauger
 
/lusr/bin/brain: received signal: SIGIDIOT

_______________________________________________
rock-devel mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCtn8QPNIEsfpKDdERAtM2AKCNezdUg95NSfxZqey/Lst152j/bwCdGT6L
gjDu7Lju8oMScTxgdB2P57U=
=LRwT
-----END PGP SIGNATURE-----