| 1 |
On Sunday 13 November 2005 00:34, Chris Gianelloni wrote: |
| 2 |
> On Sat, 2005-11-12 at 13:39 +0900, Jason Stubbs wrote: |
| 3 |
> > On Saturday 12 November 2005 07:19, Stuart Herbert wrote: |
| 4 |
> > > When we have emerge --news done, |
| 5 |
> > |
| 6 |
> > I keep seeing references to "emerge --news" but at the same time am |
| 7 |
> > seeing that news readers are external. What exactly is `emerge --news` |
| 8 |
> > meant to do? Print out "You've got news!"? Manage some external database? |
| 9 |
> |
| 10 |
> It is my opinion that the news reading application need not be |
| 11 |
> integrated into portage. As far as I have understood it, the only real |
| 12 |
> thing that anyone has required portage itself to do is to |
| 13 |
> *automatically* spit out "You have $n unread news messages. Please use |
| 14 |
> $bleh to read them" at certain times (after sync, after --pretend, |
| 15 |
> before/after a merge). I don't see this as being something very |
| 16 |
> complex. I would assume that some extra code would need to be written |
| 17 |
> into the sync code somewhere to sort the messages. |
| 18 |
|
| 19 |
This, I get. What I'm wondering about is the `emerge --news` that is referred |
| 20 |
to every so often. |
| 21 |
|
| 22 |
> I wouldn't mind seeing something along the lines of /var/db/news |
| 23 |
> directory (or something repo specific, whatever) that has a pretty |
| 24 |
> simple format... |
| 25 |
> |
| 26 |
> yyyy-mm-dd-$blah-$lang.txt.unread |
| 27 |
> yyyy-mm-dd-$blah-$lang.txt.read |
| 28 |
> |
| 29 |
> When you delete a message, it is gone. This means an external news |
| 30 |
> reader (enews anyone?) that basically has the capability to read, skip, |
| 31 |
> or delete these news items. |
| 32 |
> |
| 33 |
> I think this would be pretty simple to get done and covers the problem |
| 34 |
> of messages being read or unread. Of course, this is all just an idea, |
| 35 |
> so feel free to blow holes all in it. ;] |
| 36 |
|
| 37 |
To be honest, this is the part that I don't like the most. Integrating code |
| 38 |
into portage to copy files here and there based on some predefined rules and |
| 39 |
news readers reading and renaming files based on some predefined rules... |
| 40 |
A filesystem based API just doesn't seem very robust to change. |
| 41 |
|
| 42 |
I'd prefer that either the post-sync handling code is not integrated into |
| 43 |
portage and portage just triggers some external script - or - portage exposes |
| 44 |
an API (via python and bash) for accessing and updating news items. I'd |
| 45 |
prefer the latter but I get the impression that most prefer the former. |
| 46 |
|
| 47 |
-- |
| 48 |
Jason Stubbs |
| 49 |
-- |
| 50 |
gentoo-dev@g.o mailing list |
Archives