1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Chris Gianelloni wrote: |
5 |
> On Tue, 2005-11-01 at 12:26 +0000, Ciaran McCreesh wrote: |
6 |
> |
7 |
>>On Tue, 01 Nov 2005 13:16:03 +0100 Thierry Carrez <koon@g.o> |
8 |
>>wrote: |
9 |
>>| For them to know about it, they need to be warned when they do their |
10 |
>>| "emerge -p world" or "emerge -a mysql" that the upgrade is not as easy |
11 |
>>| as it seems. People using a cron job to sync are probably a |
12 |
>>| significant part of our user base... |
13 |
>> |
14 |
>>Have Portage give a red flashy before emerge if there're unread news |
15 |
>>items? |
16 |
> |
17 |
> Or have it die unless they have |
18 |
> I_LIKE_A_BROKEN_SYSTEM_PLEASE_IGNORE_NEWS="yes" in make.conf.... ;] |
19 |
> |
20 |
>>Although, a better solution for users who cron sync would be to have |
21 |
>>said cron mail them all the relevant news files... |
22 |
> |
23 |
> We don't have control over what they do in cron, we do have control over |
24 |
> portage itself. |
25 |
> |
26 |
|
27 |
The cron thing is a *really* good idea. Its so good that its an example |
28 |
in the Gentoo Cron How-to. A few developers actively debugging the sync |
29 |
process might enjoy watching the output of a sync scroll by, but |
30 |
normal/sane people have better things to do. (Note: I'm not bashing |
31 |
Chris's statement here; I honestly don't know what point he was trying |
32 |
to make). |
33 |
|
34 |
So don't implement the --news thing in such a way that in the future a |
35 |
developer might be tempted to tell a complaining user "whats the matter |
36 |
with you? don't you read the output when you sync? no? what a loser; no |
37 |
wonder your system is b0rked." (or something to that effect) |
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v1.4.1 (GNU/Linux) |
40 |
|
41 |
iD8DBQFDarFQ2QTTR4CNEQARAgWDAJ0cW1xpOKCy+jjaYCoGBbfOOXSGwwCgojNk |
42 |
flBm0MnXXXRLsBGC3XXcYts= |
43 |
=1Ls9 |
44 |
-----END PGP SIGNATURE----- |
45 |
-- |
46 |
gentoo-dev@g.o mailing list |