1 |
El jue, 25-11-2021 a las 09:20 -0500, Mike Gilbert escribió |
2 |
[...] |
3 |
> I don't like the phrase "forcefully downgraded" here. This implies |
4 |
> > > that something happened without the user's consent. emerge would have |
5 |
> > > informed them of the downgrade before it happened. I would suggest |
6 |
> > > removing the word "forcefully" from these paragraphs. |
7 |
> > |
8 |
> > If you do a normal world upgrade, this is the default portage behavior, |
9 |
> > not? I.e. package manager will downgrade if you don't stop. And |
10 |
> > especially on servers, people tend to use cronjobs/scripts to do that... |
11 |
> |
12 |
> Something happening by default is not the same as forcing it to happen. |
13 |
> |
14 |
> Using a cron job or other blind automation to do package upgrades on |
15 |
> any production system is a bad idea. We certainly do not recommend |
16 |
> that to people, nor force them to do it. |
17 |
> |
18 |
> |
19 |
|
20 |
As a side note, maybe ebuild should add sanity checks (like those from glibc) to |
21 |
prevent downgrades, otherwise people could still accidentally hit the issue |
22 |
|
23 |
Thanks |