Re: make xconfig broken in bk current

[John Levon <levon@movementarian.org>]

On Sun, Jan 12, 2003 at 10:03:49PM +0100, Sam Ravnborg wrote:

> I would like to see it stay within the kernel for the following reasons:
> 1) It works as it is for those who have QT
> 2) It's more appealing to some people with a grapical frontend
> 3) If it fails, people can revert back to menuconfig
> 4) It does not take up much space. ~2 files
> 
> The problem seems that some people does not like the QT choice.
> But only one attemp has been made (that I know of) implementing
> an alternative graphical frontend. (Romain Lievin - GTK)
> 
> I you do not like the QT version - don't use it.
> If too many people post error - get it fixed.
> Simple...

I do not want it removed because it's a graphical frontend, or because
it's using Qt. I want it removed because it is an inappropriate package
to have it in.

All else being equal, code should not be in the kernel package. Please
explain the *advantages* of including it in the same package.

moc binary detection is broken, btw if the qt dir guessing is used (a
bad idea in the first place). That's just an obvious one, there are
undoubtedly other problems.

Sorry but it's just bizarre having patches for some GUI going through
lkml

regards
john
-- 
Khendon's Law: If the same point is made twice by the same person,
the thread is over.