Ciaran McCreesh wrote: > Paludis producing a warning (as opposed to a lower level notice -- > Paludis has different levels for log notices, of which 'warning' is > the highest) is something that is considered critical enough that the > user should fix it before continuing. Were it not critical, a different > log level would be used. Paludis log levels are irrelevant. The recent change in the cups.conf is no more or less critical that the one in Paludis: something changed without causing things to breaks --> it is not critical, as it wont be more or less work to fix it before or after running the application again, although doing so beforehand is perferred. You say it yourself: "the user should fix it before continuing" "should" not "has to" It is critical if your filesystem might be damaged, if there are security issues of any kind, or if something stops working.
A simply warning because a deprecated config format is used, just aint critical. If I am wrong here, I bet the majority of Gentoo developers would jump in and start correcting me. If they wont, I would suggest you just accept this, and use einfo or whatever you like to. By doing so you alone would be able do save each and everyone of us reading this list time and/or bandwidth. > This thread is not, however, about Paludis. Please keep future moaning > about Paludis in the appropriate thread. Perfectly correct, it is about this news item being critical or not. I were not the one who started to talk about log levels, which is off-topic. -- [EMAIL PROTECTED] mailing list
