Eric S. Raymond writeth: > Yes, this will lead to large ugly expressions, but those large ugly > expressions will be in *one place*. In the kernel rulebase, the correct > "one place" is with the other cross-architecture stuff in the toplevel > rules.cml file.
And this is a good thing? I speak as a forayn freke here, but as I recall the purpose of this feature was to allow each duke to specify the list of things critical to his particular fiefdom, requiring a complete rebuild if changed. Placing this large ugly expression in the royal demesne will require that whenever a new critical element is found for *anybody*, the Tsar of All the Distros will have to issue a new ukase. This seems to be against the principle of subsidiarity. Allowing modular derived symbols will allow independent control. I urge to you reconsider. -- John Cowan http://www.ccil.org/~cowan [EMAIL PROTECTED] Please leave your values | Check your assumptions. In fact, at the front desk. | check your assumptions at the door. --sign in Paris hotel | --Miles Vorkosigan _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
