Peter Samuelson wrote: > > > So now we assume BK? What's next, Python 2.1? > > Touché. No, my point was not that we can assume BK, but that we can > assume the developer is willing to install whatever tools he needs to > get the job done. > > I think the assumption is valid, assuming the developer has some > choice in the matter - i.e., do not dictate a specific SCM or even a > specific version of gcc (though there is a fairly limited range of > acceptible gccs).
I think in theory this is a good rule well stated, but in practice we start to get into some tricky areas. What if the definition of "any SCM tool to get the job done" narrows to the point where there's basically one choice, as with the compiler? Or if it narrows just sufficiently to exclude CVS? I agree we can't support every possible SCM tool in the universe, but there's a lot of impact in the details of where we're willing to draw the line between an SCM "good enough" and one that's not. My point is that if we draw this line such that CVS is on the "good enough" side, we will need to do the shadow tree support outside the SCM, either in kbuild or in your postulated wrapper for kbuild. > [...] Anyway, the > "cobble together" script will most likely build a symlink tree, not a > whole separate copy, so you probably wouldn't have to rebuild it > *every* compile. Interesting. > At least, if I were writing an ad hoc shadow tree preprocessor, that's > how I'd do it. Then when you are just fixing one-liners, you aren't > adding or removing files from the tree so you don't rebuild the link > forest. Well, why don't you write such a thing, so we can compare and contrast with kbuild2.5's approach? I believe that kbuild2.5's approach will stand scrutiny. > > Here's part of a brand new checkout: > > [...]If you have a brand new checkout, you probably don't > have a preexisting set of object files yet, so I'm not convinced that > you can actually break your compile this way. Personally, this doesn't bother me so much, I've never really had the bad luck to trip over some of the truly pathological cases in the kernel. I just wanted to point out that it's not a totally imaginary problem. Greg. -- the price of civilisation today is a courageous willingness to prevail, with force, if necessary, against whatever vicious and uncomprehending enemies try to strike it down. - Roger Sandall, The Age, 28Sep2001. ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
