On 23 Oct 2002, Guillaume Cottenceau wrote: > That counts, but I don't agree with the axiom "because users want > it, we do it". Sometimes we don't agree and we don't do it. I > have to agree to do it. I was taking a rather severe stance. Ofcourse you have a free will, but I think you are not as free as a gernal OSS developer because you work for mandrake.
> > It wasn't an example, or I didn't understand it. Think you looked at the wrong mail. I was talking about MTA example. In short: I search for program doing X, I search in descriptions for X, but I have to use 2 different programs to check whether I already have one, and if not, to see what the options are. > > If the point was really to have "some way of searching for a > package when I don't know if it is installed or not", I yes, or a description/file. > personally do "rpm -qa package*", people can do it with rpmdrake > or rpmdrake-remove I suppose? It is one "concept": looking for package X. It is silly to use 2 programs for it. > > It would be quite easy to add it to the code of the installing > package version, but the main problem is how does it integrate > with the UI? If you can provide a good design I do agree with, > I'll add it. I agree. >A good design requires that we don't add any other > visible UI element. That sounds strange. How to add a feature without UI element? Or do you mean it has to be kinda hidden (like the search description/names button) Danny
