On Saturday, May 5, 2007 03:23:41 PM Ciaran McCreesh wrote: [Paludis configuration: * -> */*] > Experience and user feedback has shown that in situations like this > users want an accompanying news item even if the application does > output deprecation warnings.
Currently, there are two news item in the Paludis overlay. Unless earlier ones were removed, those two seem to be a fairly small sample to deduce anything from. Furthermore, GLEP42 states: "News items must only be for important changes that may cause serious upgrade or compatibility problems. Ordinary upgrade messages and non-critical news items should remain in einfo notices." 2007-05-04-paludis-0.24 doesn't fit this description. That isn't the real problem, though. The real problem with issuing news items for trivial changes is that people will just start marking such news items read without really reading them or even stop synching news items completely. We won't gain anything implementing GLEP42 if people get the impression we're issuing news items for configuration changes that the application in question warns about anyway. For such information as contained in the Paludis 0.24 news item a better description of how to get ebuild messages stored/mailed/whatever might achieve much more. Seeing that something as trivial as mailing ebuild messages to the administrator requires using Paludis' hooks (cf. http://paludis.pioto.org/hooks.html#ebuild-message-hooks) which is not something that can be expected from a normal user (quoting yourself, Ciaran: "the users are idiots"), it seems worthy to work on improving that. Then, elog and friends would be fully sufficient for informing users about such configuration changes - under the circumstances of this case at least. Best regards, Wulf
pgpzphVF9bmUH.pgp
Description: PGP signature
