Shawn Walker wrote: > Right; which again is why I think we shouldn't bother worrying about > "tools already provided." It's probably simplest just to build and > install all of them and be done with it. That we can be certain that > we have a consistent environment with identically configured tools. > > It works wonderfully too (except for the minor nits I mentioned in my > initial response to this thread). > > Again, it's great; I just wouldn't change anything about the build or > which tools get built / installed.
after some deliberation, I actually think that's better than having some magical tool selection going on behind the scenes. I do think Lukas' suggested scheme would work, but considering a) the fact that this kind of scheme *does* address a moving target, and therefore needs maintainance, and b) my opinion that the number of build machines will hopefully be outnumbered by far by the number of machines where KDE will be installed, I think we(*) should invest further effort in kde itself, not in some relatively minor optimisation of the very good build environment. Michael *) I'm very free with "we" here, I know, seeing I haven't invested anything much so far ;-) -- Michael Schuster Sun Microsystems, Inc. recursion, n: see 'recursion'
