On Tue, Jan 22, 2013 at 3:03 AM, Alexander Berntsen <alexan...@plaimi.net> wrote: > > While I tend towards the cleaner design, not the "don't fix what isn't > *broken*" approach -- I'm fine either way. But I think the handbook or > some tool should obnoxiously spit the flags (and a minor > "justification" for each flag and/or the set of flags) of each profile > in your face when you are at the "set a profile" step of the > installation. This way it can clarify that the user might want to > disable some of the profile-enabled flags.
Not really sure that adds much value. A few users might want to disable everything, but just as many if not more are likely to want to enable stuff that is disabled. Should we therefore list all the flags on the system and which ones are enabled and disabled? I guess we could, but it is a REALLY long list. In practice I find that the way I tend to use USE flags is that I just ignore them until something unexpected happens, and then change them. Rich
