> A multiple-apex tree also tends to pull the configuration questions downwards
> from policy (e.g "Parallel-port support?") towards hardware-specific,
> platform-specific questions ("Atari parallel-port hardware?") By designing
> the configuration rules for CML2 as a single-apex tree, I'm trying to
> move the questions upwards and have derivations in the rules file handle
> distributing that information to a lower level.
Ok I see where you are going with that argument. However when you parse all
the existing Config.in files into a tree you can see those properties by
looking from any node back to its dependancies
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:17 EST