1 |
On Sunday 11 December 2005 10:35, Ciaran McCreesh wrote: |
2 |
> Whenever relevant unread news items are found, the package manager will |
3 |
> create a file named ``/var/lib/portage/news/news.unread`` (if it does not |
4 |
> already exist) and append the news item identifier (eg |
5 |
> ``2005-11-01-yoursql-updates``) on a new line. |
6 |
> |
7 |
> .. Note:: Future changes to Portage involving support for multiple |
8 |
> repositories may require one news list per repository. Assuming |
9 |
> repositories have some kind of unique identifier, this file could be named |
10 |
> ``news-repoid.unread``. |
11 |
|
12 |
Repositories will definitely have a unique identifier. Perhaps it would be |
13 |
better to use the repository-identifing format from the beginning so that |
14 |
readers are forced to be forwards-compatible? Assuming the readers would then |
15 |
output the repository name, labeling it "gentoo" should work well... |
16 |
|
17 |
> When a news item is read, its name should be removed from the |
18 |
> ``news.unread`` file. News clients may add the name to a ``news.read`` file |
19 |
> in the same directory with the same file format. |
20 |
|
21 |
news.read should either be mandatory or not created at all. Should a user |
22 |
change from a reader that creates and uses the file to one that doesn't and |
23 |
then change back again the results will be unexpected. |
24 |
|
25 |
> * Important: there are 5 unread news items. |
26 |
> * Type emerge --help news to learn how to read news files. |
27 |
[...] |
28 |
> An ``eselect`` [#eselect]_ module shall be created as the 'suggested' |
29 |
> display tool; other display tools (for example, a news to email forwarder, |
30 |
> which would be ideal for users who sync on a ``cron``) are left as options |
31 |
> for those who desire them. |
32 |
|
33 |
By "suggested" you mean that it should be referenced in the news help? |
34 |
|
35 |
-- |
36 |
Jason Stubbs |
37 |
-- |
38 |
gentoo-dev@g.o mailing list |