1 |
2009/10/12 Jesús Guerrero <i92guboj@×××××.es> |
2 |
|
3 |
> |
4 |
> But there's one... That what the "system" set is about in first place. We |
5 |
> could argue if creating a new category would be any good or not, that's a |
6 |
> different issue. But there's already a list of packages that's considered |
7 |
> critical for a Gentoo system. That's what "system" is, and you will get a |
8 |
> big red waning when trying to uninstall one package belonging to this |
9 |
> category. |
10 |
> |
11 |
|
12 |
My point would be that the selection criteria isn't particularly |
13 |
robust/strict. Iptunnel, df or du for example are not required to the best |
14 |
of my knowledge for system booting or emerges. Dev-lang/python is on the |
15 |
other hand required for emerging (and is not a "sys" package). I'm also not |
16 |
sure that the warnings are strict enough. In order to upgrade a package |
17 |
(util-linux I think) recently I had to unmerge a library package on which it |
18 |
depended but which conflicted with an upgrade to said library. The unmerge |
19 |
of the library package broke either fsck or mount (I can't remember which). |
20 |
Had I tried to reboot before the upgrade was completed there would have been |
21 |
problems. |
22 |
|
23 |
Big "red warnings" are of no use when one is doing semi-automatic-upgrades |
24 |
(and colored encodings are normally disabled when one dumps the emerge |
25 |
output to a file). What is needed is a separate indicator in emerge outputs |
26 |
indicating that an upgrade is potentially "Dangerous" or should require |
27 |
"Manual" intervention. Anyone who is not a full time developer but who |
28 |
wants to maintain a relatively up-to-date Gentoo system (which IMO is its |
29 |
primary advantage over "packaged" releases such as RedHat, Ubuntu, etc.) is |
30 |
going to want to automate the nightly emerges as much as possible such that |
31 |
no user intervention is required. And that probably works 90% of the time. |
32 |
But there are those 5% of emerges that fail "reasonably" and require some |
33 |
intervention (e.g. bug reports) and those 0.1-1% of emerges that fail (or |
34 |
even succeed) with potential problems that could cost the user days. It is |
35 |
that final category (and it isn't every binary produced by a sys* package) |
36 |
that I am suggesting warrants more attention. |
37 |
|
38 |
Robert |