So there are four "news" in total and one is from 2007.

I disagree. This is the best place to announce package installation related stuff: straight after you sync the Portage tree. And it gets noticed with 100% confidence.Ormaaj wrote:This is a job for a feed-reader; Not a configuration tool, or a package manager.

In this case, no. This mechanism is to ensure news items of critical importance cannot be missed.Ormaaj wrote:Wouldn't it be better to distribute news through some already established standard than to invent a new gentoo/portage-specific tool? ... This is a job for a feed-reader; Not a configuration tool, or a package manager.

Yup. I couldn't agree more.Paapaa wrote:I disagree. This is the best place to announce package installation related stuff: straight after you sync the Portage tree. And it gets noticed with 100% confidence.Ormaaj wrote:This is a job for a feed-reader; Not a configuration tool, or a package manager.
Code: Select all
hikaru ~ # eselect news list
Unread news items:
(none found)
Read news items:
(none found)
hikaru ~ # rm /var/lib/gentoo/news/news-gentoo.*
rm: cannot remove `/var/lib/gentoo/news/news-gentoo.*': No such file or directory
hikaru ~ # find /usr/portage/metadata/news -mindepth 1 -type d -printf "%P\n" >/var/lib/gentoo/news/news-gentoo.unread
hikaru ~ # eselect news list
Unread news items:
(none found)
Read news items:
(none found)
hikaru ~ #
Code: Select all
hikaru ~ # ls /usr/portage/metadata/news/
2007-05-04-paludis-0.24 2009-01-04-sparc-multilib 2009-04-06-tetex 2009-04-06-x_server-1_5 timestamp.chk


News items are filtered by what the news item specifies:yabbadabbadont wrote:I was presented with the news item for the xorg update, but there were three other, older, items there that I had never seen. I'm guessing that I didn't see them either because none of them applied to my system (sparc, tetex, and paludis)

So I can't automate syncs if I want to be notified of these news items?yabbadabbadont wrote:In other (more obvious) words, in the status messages that are displayed at the end of an "emerge --sync" operation.V-Li wrote:If the news item applies to you, you will be informed similar to changed configuration files.arnvidr wrote:So where do these news show up automatically?
Noone wrote:anything

Mail yourself the output of the sync job (and read itarnvidr wrote:So I can't automate syncs if I want to be notified of these news items?
Code: Select all
#!/bin/bash
if [ $(eselect news count) -ne 0 ] ; then
eselect news list
fiNoone wrote:anything

Like everything else in the tree, news items deleted upstream would be removed when you sync. However, I would not expect that to happen often, given the importance of news broadcasting and the possibility of long sync intervals for some users.arnvidr wrote:[D]oes the list of read news items get shortened once in a while?
arnvidr wrote:I don't have it really automated, but I have an alias that updates overlays and stuff after it syncs the tree, but I guess I could just change the order, or put eselect news list at the end of the operations. One question though, does the list of read news items get shortened once in a while? I'm really not interested in reading news from 2007 about a program I've never used.