1 |
On 06/30/2012 11:33 AM, Andreas K. Huettel wrote: |
2 |
> Am Samstag 30 Juni 2012, 13:22:39 schrieb Zac Medico: |
3 |
>> On 06/30/2012 04:07 AM, Pacho Ramos wrote: |
4 |
>>> I would like to discuss a bit more issues like: |
5 |
>>> https://bugs.gentoo.org/show_bug.cgi?id=423087 |
6 |
>>> |
7 |
>>> Even if there are "a lot" of packages that can cause this breakage when |
8 |
>>> downgraded, I think it should be prevented and package managers |
9 |
>>> shouldn't try to downgrade this kind of packages as they will later |
10 |
>>> cause a total breakage. People is not supposed to know that downgrading |
11 |
>>> some package system will, for example, have an unusable gcc. |
12 |
>> |
13 |
>> It seems like a die in pkg_pretend would serve pretty well. |
14 |
> |
15 |
> As a comparatively simple, user-oriented workaround, since this only happens |
16 |
> at downgrades and these should be pretty rare, I have the following |
17 |
> suggestion: |
18 |
> |
19 |
> Make a portage feature that is **on by default**, which causes portage to |
20 |
> generate a binpkg of the version to be unmerged, in the case of a downgrade. |
21 |
> |
22 |
> Rationale: |
23 |
> * if you know what you are doing, you can switch this off easily |
24 |
> * does not take much space since downgrades are rare |
25 |
> * should help our users a lot, whenever someone accidentally or not-knowingly |
26 |
> downgrades something critical. |
27 |
> |
28 |
> Thoughts? |
29 |
|
30 |
I like that idea. I've filed this bug: |
31 |
|
32 |
https://bugs.gentoo.org/show_bug.cgi?id=424275 |
33 |
-- |
34 |
Thanks, |
35 |
Zac |