On 3/10/06, Rahul Sundaram <sundaram@xxxxxxxxxxxxxxxxx> wrote: > gb spam wrote: > >Rahul said a number of times that the cost was high. When asked to > >quantify what high meant, he neglected to answer. My suspicion is > >that it would be high on pride. > > > > > Nothing to do with pride since I did give you the answer. Its a choice > between spending time on the list discussions or go back and do actual > work and people have pointed out to me ( by swearing at me offlist) that > the balance currently is tilted towards discussions. I have already > explained several times on the list that Anaconda code has been > rewritten to use yum and this feature has to be *reimplemented* now and > the Anaconda developers told me that the code to reimplement this would > be significant and they dont see enough merits to do so. Combine that > with the effect of this "feature" and the time spend in fixing and hand > holding new users who choose to use this option innocently and we land > up with a high cost I cited. and still there is no quantification of "high". if i said that not having an everything install button has a high cost, would you accept that if i just continued to wave my hands in the air? (please don't take this as abuse or anger, i just have trouble accepting something when a question is not answered several times) > Combine that > with the effect of this "feature" and the time spend in fixing and hand > holding new users who choose to use this option innocently If there are problems merely because multiple packages are installed together, that is entirely another problem, which should _also_ be dealt with. we shouldn't be trying to hide from those problems. on the contrary, we should be looking for them. if one problem comes up frequently (like the oft-cited gfs kernel) then it quickly becomes a known problem, work arounds are made public, mailing lists are well aware of the problem and can direct people experiencing them in the right direction and hopefully the problems also get resolved too. the net result being that the project wins in the long run. this is actually the direction we should be aiming for, not shirking away from.
