1 |
On Mon, 2006-08-07 at 15:01 +0200, Enrico Weigelt wrote: |
2 |
> Lets say, if I've, installed foo-1.1, and it gets masked due |
3 |
> some bug(s), but 1.0 isn't, I want to get informed with an big |
4 |
> fat warning, *before* anything actually done, ie. |
5 |
> |
6 |
> [...] |
7 |
> # WARNING: installed package foo-1.1 has been masked and would |
8 |
> # be downgraded: |
9 |
> # <masking comment ...> |
10 |
> [...] |
11 |
> |
12 |
> An fully-automatic downgrade should *never* downgrade anything. |
13 |
> This is too dangerous, because essential features can get lost. |
14 |
> Again, my bugzilla example: assuming 2.22 will be unmasked some |
15 |
> day and I installed it w/ postgres support. Now there are some |
16 |
> bugs found, but not fixed fast enough, so it gets masked. |
17 |
> I run an update w/o knowing that it downgrades, and my whole |
18 |
> bugzilla hosting is suddenly broken. |
19 |
|
20 |
That would not happen. bugzilla is a webapp and as such is fully |
21 |
SLOTted. Upgrades (and downgrades) are manual. |
22 |
|
23 |
Ed |
24 |
|
25 |
-- |
26 |
gentoo-dev@g.o mailing list |