1 |
1.11.2005, 13:48:06, Ciaran McCreesh wrote: |
2 |
|
3 |
> | The messages should be displayed when I'm about to upgrade an ebuild |
4 |
> | which has an upgrade note associated with the new version. Sending |
5 |
> | mail via cron might be a nice optional feature for those who want to |
6 |
> | use it. |
7 |
|
8 |
> Not really a good idea, a) because news items aren't tied directly to |
9 |
> ebuilds, and b) because people like advance warning of "when you |
10 |
> upgrade Apache, all hell will break loose!" rather than having it |
11 |
> sprung on them suddenly when they're trying to do a quick update. |
12 |
> Getting the news item in advance allows for planning. |
13 |
|
14 |
What do you mean "they aren't tied to ebuilds"? I don't really understand what |
15 |
this feature should do then, it seems. Once again, what's wrong with reusing |
16 |
emerge --changelog mechanism for displaying this kind of information? |
17 |
|
18 |
I'm not particularly happy with idea of emerge as a newsreader really, IMHO we |
19 |
should display relevant, vital upgrading information *when relevant*, not to |
20 |
inform users about upgrades that they are not interested in in the least. |
21 |
Example: Don't bother me with mysql-4.1 upgrade instructions, I don't plan to |
22 |
upgrade to that version and did put it into package.mask. Another example: |
23 |
Don't bother me with upgrade instructions for ~arch ebuilds, I'm running |
24 |
stable. I want to read them when I decide to upgrade, put them into |
25 |
package.keywords and run emerge -uav someebuild/world or when it goes stable. |
26 |
|
27 |
And please, keep the thing simple so that I can be done in reasonable amount of |
28 |
time and does not follow the destiny of einfo/ewarn logging (3 years and |
29 |
counting). |
30 |
|
31 |
|
32 |
-- |
33 |
Best regards, |
34 |
|
35 |
Jakub Moc |
36 |
mailto:jakub@g.o |
37 |
GPG signature: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xCEBA3D9E |
38 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
39 |
|
40 |
... still no signature ;) |