Jeff Garzik <jgarzik@mandrakesoft.com>:
> Global dependencies... CML1 doesn't have this now, and it needs never
> to have it. This is no point in merging a design change of that
> magnitude only to take it away later on. Further, merging a rulebase
> which contains such dependencies would be a huge mistake that might take
> years to undo. drivers/net/rules.cml doesn't need S/390 stuff in it,
> AFAICT, and that is a simple example of a bug found in many of the
> rules.cml files.
All right. There are a couple of ways we can attack this -- I have
some ideas. But I want a meta-question answered first. If we solve
this issue, *are you on board*?
I've got to get off the fscking treadmill I'm on now where I'm spending
so much time on the parallel-rulebase maintainance and the flaming
politics that I can't really get anything else done.
After what you wrote upthread, I don't think you want me to be stuck
either. Fact: ain't nobody else visible with both the motivation and
skills to tackle what you want done. I've been thinking about
metadata-centered configuration and consciously bending CML2's design
towards it for longer than anyone else has even been considering the
problem.
I *will* get us there -- I think the last two years have demonstrated
my determination. But to do it, I need alliance rather than
obstruction. I need you to tell Linus that your concerns have been met
and sponsor CML2 to go in, so I can stop perpetually re-fighting old
battles.
Because we agree on getting to metadata-centered configuration, your
requirements list now appears to have shrunk to one. You want to
"eliminate global depencies". I hear that. I got it.
What I want to know is that this is not a proxy for "CML2 can never be
good enough" and that you'll be pulling more objections out of your butt
till the Sun goes nova. Because if that's true there's no point in
my trying to work with you.
But if "eliminate global depencies" is it, we can be allies, because
ultimately we both want to get the config system to the same place.
I've taken the first, biggest step -- from imperative code to
declaration/constraint language. The second -- from a
declaration/constraint language to a metadata-centered system --
will be easier.
A positive answer may be "Yes, that's it, let's go forward", or
"Almost, there are a couple other minor and negotiable issues *which I
will now list*" (where "Minor and negotiable" = "I don't have to scrap
my architecture").
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a> - 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 : Sat Feb 23 2002 - 21:00:12 EST