| 1 |
Two things. |
| 2 |
|
| 3 |
One, if users run --sync in a cronjob, which many do, this preemptive |
| 4 |
goes out the window. |
| 5 |
|
| 6 |
Two, an alternative to that, if we are all recoding portage anyways :) |
| 7 |
Have portage place a special note next to any items with relevent |
| 8 |
news when -a or -p is passed, and then, emerge --news cat/package |
| 9 |
could show relvent stuff, or --news to see it all. |
| 10 |
|
| 11 |
On 11/1/05, Georgi Georgiev <chutz@×××.net> wrote: |
| 12 |
> maillog: 01/11/2005-11:45:08(+0100): Jakub Moc types |
| 13 |
> > 1.11.2005, 11:00:22, Thierry Carrez wrote: |
| 14 |
> > |
| 15 |
> > > Aren't those messages displayed after the damage is done ? Typical use |
| 16 |
> : |
| 17 |
> > |
| 18 |
> > > - emerge --sync run as a daily cron job |
| 19 |
> > > - emerge -a mysql |
| 20 |
> > > - great, a new version is there. Typing "Yes" |
| 21 |
> > > - system gets borken |
| 22 |
> > > - emerge spits out message saying 14 files need updating and there is 1 |
| 23 |
> > > unread news item |
| 24 |
> > |
| 25 |
> > > I'm probably missing something here. Please elaborate on how this GLEP |
| 26 |
> > > meets the "Preemptive" design goal... |
| 27 |
> > |
| 28 |
> > |
| 29 |
> > I'm probably missing something obvious here, because I can't see why |
| 30 |
> *existing* |
| 31 |
> > emerge --changelog code cannot be recycled for this feature to display |
| 32 |
> upgrade |
| 33 |
> > messages when running emerge -uDav world... |
| 34 |
> |
| 35 |
> That reminds me of the idea to stick tags in the ChangeLog: |
| 36 |
> http://groups.google.com/group/linux.gentoo.dev/msg/8f2dc84619be5c5b?fwc=1 |
| 37 |
> |
| 38 |
> But still, I'm guessing the idea of "--news" is to tell people that they |
| 39 |
> need to do something A.S.A.P. This means as soon as the news are |
| 40 |
> obtained, and the users are nagged about the news on *every invocation |
| 41 |
> of emerge*, similar to the /etc messages, and not only when they decide |
| 42 |
> to install some package, which is when --changelog kicks in. |
| 43 |
> |
| 44 |
> And then, I am not sure why glsa-check cannot do the same job... |
| 45 |
> |
| 46 |
> -- |
| 47 |
> () Georgi Georgiev () Computers are unreliable, but humans are () |
| 48 |
> () chutz@×××.net () even more unreliable. Any system which () |
| 49 |
> () http://www.gg3.net/ () depends on human reliability is () |
| 50 |
> () ------------------- () unreliable. -- Gilb () |
| 51 |
> |
| 52 |
> |
| 53 |
|
| 54 |
-- |
| 55 |
gentoo-dev@g.o mailing list |
Archives