After emerging kdemultimedia, there's no sign of kaudiocreator. In KDE 3.1, it was only built with USE=cdr, but in the KDE-3.3.1 ebuild there's no sign of useflag-dependent building fo kaudiocreator. What's going wrong? kde-base/kdemultimedia-3.3.1 +alsa +arts -audiofile -cdparanoia -debug +encode +flac +oggvorbis +speex +xine -xinerama
This surely has confused a lot of users: kaudiocreator is built only if the 'cdparanoia' use flag is enabled. If only an ebuild could specify that a local flag should be enabled by default...
Interesting: On my other machine I have kdemultimedia-3.3.1 *with* kaudiocreator, although I don't have cdparanoia in the useflags as well, so I didn't check that flag. Strange Why a special useflag at all for kaudiocreator? It doesn't bloat KDE IMHO...
Mainly to avoid forcing a dependency on the cdparanoia package for everyone. I don't know why the other machine has it, though.
I guess cdparanoia was installed by some other software and KDE autodetects cdparanoia, thus installing kaudiocreator. Still, I'd appreciate a comment in the ebuilds about the effects of the deps, makes "debugging" much easier. cdparanoia might make a ood default useflag, it's really small and very useful.
>Why a special useflag at all for kaudiocreator? It doesn't bloat KDE IMHO... In the few cases I tried to use reasonable defaults and not to give the user the chance to get stuck, I promptly got some bug report, requesting to change the default, resulting in another use flag in the end. I don't like the use flag hell, but we cannot add comments for all and everything. Especially since this is a compile time issue and usually you don't sit in front of your box, watching the output of the emerge output. Also it's not worth the increased maintenance cost to take the user by the hand for all and everything. This is not Suse. At best ebuilds should install w/o having to notice any information except the need to run etc-update, to modify/update configuration files. There are ideas floating around, having use flag groups, special profiles, prefixed flags and so on to provide better defaults, but until now, no one came up with an idea without serious downsides. The ease to configure your system as you like implies, that you have to keep up with increased complexity. I think Gentoo may come to the point (another thousand use flags or so), that it's necessary to cut that down, resulting in less complexity/choice, but I don't think it'll happen until it really hurts a majority of users to run into such issues.
Changing to invalid since the ebuild works. Just a problem with too many useflags floating around...
