-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/11/12 08:19 PM, Jauhien Piatlicki wrote:
> 03.11.12 09:04, Ben de Groot написав(ла):
>> On 31 October 2012 23:17, Chris Reffett <[email protected]>
>> wrote:
>>> Basically, I would rather the user get too many elog messages
>>> than not enough, since I feel that a lot of people skip over
>>> them anyway and so the "only display once" method makes it far 
>>> too easy for important messages to get lost in the shuffle.
>> 
>> Did you ever consider *why* so many users skip over elog
>> messages? Don't you think that could be because most of these
>> messages of useless to them, or they have already seem them many
>> times?
>> 
>> I think we need to come up with a better policy regarding elog 
>> messages, which would improve the signal to noise ratio.
>> 
> 
> Yes, it would be really great if messages that are not relevant
> for upgrading of a package will be shown only for the first
> install. For example, I've just finished upgrading of Gentoo on my
> notebook and I was spammed with heaps of messages. They are for 10
> packages. From them messages for net-misc/dhcpcd, net-misc/tor,
> sci-physics/root, mail-client/thunderbird, www-client/firefox and
> sci-libs/scipy are typical and not relevant for update. It means
> for 6 from 10 packages (Only message for dev-libs/boost is quite
> original with its red color )) ). It is of course not very
> important issue, but it is quite annoying.
> 
> 

As of EAPI=4 (i think? maybe 3?) ebuild authors can use a simple test
to see if $REPLACING_VERSIONS is empty or not to indicate whether the
package is being newly installed or if it's being upgraded.  Maybe, if
package maintainers are so inclined, we can start using this feature
to reduce the spam.  (if we were really motivated we could even only
provide relevant messages based on the version being replaced!)



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlCVtrUACgkQ2ugaI38ACPDOAgD+ORyGkW/Rqx4BoRWl6+172Edu
MKeVblQYLyHIkL9Y0zEA+wYDMgQblhfcHKEMW9cgLsFDkWt0dF5KiUVd1fV1SIT9
=TWem
-----END PGP SIGNATURE-----

Reply via email to