| 1 |
On Tue, Nov 01, 2005 at 08:36:23AM +0900, Chris White wrote: |
| 2 |
> Attached in plain text form is glep 42 for the discussed thread. |
| 3 |
> emerge --news support |
| 4 |
> --------------------- |
| 5 |
> |
| 6 |
> As already mentioned by Stuart, in this way users are bound to the one thing |
| 7 |
> guaranteed on their system: Portage. Through portage, the same location where |
| 8 |
> etc-update notifications are displayed (after emerge --sync and at the finish of |
| 9 |
> an emerge), will contain a notice about news updates. These news updates should |
| 10 |
> come in the form of a file contained within the portage tree for users that want |
| 11 |
> news updates on a networkless system. Should the user run these items in the |
| 12 |
> background or send the output to /dev/null for any reason, a --news option |
| 13 |
> should also be avaliable in emerge for them to review the news at a convient |
| 14 |
> time. |
| 15 |
|
| 16 |
And this file is what format? How is the format going to be |
| 17 |
structured so that emerge can know what entries to ignore? How is |
| 18 |
emerge going to pull those entries again? |
| 19 |
|
| 20 |
What restrictions are there for what goes into this file, to keep the |
| 21 |
signal to noise ratio sane? |
| 22 |
Etc. |
| 23 |
|
| 24 |
Details man, details. |
| 25 |
~harring |
Archives