| 1 |
On Tuesday 01 November 2005 08:46, Brian Harring wrote: |
| 2 |
> On Tue, Nov 01, 2005 at 08:36:23AM +0900, Chris White wrote: |
| 3 |
> > Attached in plain text form is glep 42 for the discussed thread. |
| 4 |
> > emerge --news support |
| 5 |
> > --------------------- |
| 6 |
> > |
| 7 |
> > As already mentioned by Stuart, in this way users are bound to the one |
| 8 |
> > thing guaranteed on their system: Portage. Through portage, the same |
| 9 |
> > location where etc-update notifications are displayed (after emerge |
| 10 |
> > --sync and at the finish of an emerge), will contain a notice about news |
| 11 |
> > updates. These news updates should come in the form of a file contained |
| 12 |
> > within the portage tree for users that want news updates on a networkless |
| 13 |
> > system. Should the user run these items in the background or send the |
| 14 |
> > output to /dev/null for any reason, a --news option should also be |
| 15 |
> > avaliable in emerge for them to review the news at a convient time. |
| 16 |
> |
| 17 |
> And this file is what format? How is the format going to be |
| 18 |
> structured so that emerge can know what entries to ignore? How is |
| 19 |
> emerge going to pull those entries again? |
| 20 |
> |
| 21 |
> What restrictions are there for what goes into this file, to keep the |
| 22 |
> signal to noise ratio sane? |
| 23 |
> Etc. |
| 24 |
> |
| 25 |
> Details man, details. |
| 26 |
|
| 27 |
But before details, what is the reasoning in turning emerge into an offline |
| 28 |
news reader? So that admins that don't care enough to source news information |
| 29 |
via other supported means are covered? What's the functional difference |
| 30 |
between this "emerge --news" and the existing "emerge --changelog"? I'd like |
| 31 |
bugs to be better described; should a tutorial be added to emerge as well? |
| 32 |
|
| 33 |
-- |
| 34 |
Jason Stubbs |
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives