> Is this something that should be discussed before debconf is littered > with too much information that should really have been kept in > documentation? Or should debconf be expanded into a tool to notify > users of anything about what they are just about to choose/do?
Also, does by including the amount of information in debconf right now cause our users to trust too much into that information. Instead let the users explicitly know that X types of information will be in informational debconf interactions, while Y types of information will be in README.Debian or the release notes. (not per package, but as a all encompassing thing.) -- Scott Dier <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://www.ringworld.org/ [EMAIL PROTECTED]
