1 |
Alan Mackenzie <acm@×××.de> wrote: |
2 |
> |
3 |
>> > Less clever people like me follow the handbook, and assume that |
4 |
>> > packages in @system are protected. |
5 |
> |
6 |
>> And they are right to do so. And openrc is not in @system (at least not |
7 |
>> in the profile which you have chosen), and certainly the handbook does |
8 |
>> not claim the contrary. |
9 |
> |
10 |
> Now you're getting legalistic. |
11 |
|
12 |
Yes, because gentoo follows simple rules, fortunately. One of the basic |
13 |
rules it: Put the packages which you want to use into your world file. |
14 |
You are ignoring these rules and complain. |
15 |
|
16 |
> By @system I meant "the operating |
17 |
> system", not what some legal text defines it to be. That "the handbook |
18 |
> does not claim the contrary" is poor reasoning. |
19 |
|
20 |
No, it is not. You are making the wrong assumption that for some packages |
21 |
the rules (to put into @world everything which you want to use) do not |
22 |
apply. And you make this assumption on no basis from the handbook or |
23 |
anything else. Just on a gut feeling what should be "the operating system", |
24 |
completely ignoring that "the operating system" depends on what you |
25 |
configure it to be. |
26 |
|
27 |
>> No. Putting the packages which *you* want to use into world is |
28 |
>> the most natural thing to do. |
29 |
> |
30 |
> It is unnatural to regard the operating system as a package. |
31 |
|
32 |
The operating system is not the init system. The init system is clearly |
33 |
a package, because you can have many alternatives for it. It fact, |
34 |
depending on what you need your machine for, it might be fine to have no |
35 |
init system at all. |
36 |
|
37 |
> It is natural to assume the OS won't delete itself. |
38 |
|
39 |
Indeed, and it won't delete anything crucial for your system, and even |
40 |
more, it won't delete anything what you need. But you have to tell |
41 |
portage *what* you need and *what* is crucial for your system. |
42 |
The handbook contains the instruction how to do this: Put the packages |
43 |
you need into the @world file. |
44 |
|
45 |
>> You did. You would have done the same mistake if you would have |
46 |
>> emerged systemd with the same profile without putting it into world, |
47 |
>> and have configured your boot-loader to always load systemd [...] |
48 |
> |
49 |
> Now you're trying to win an argument because you know portage etc., |
50 |
> better than me. And you're being pedantic and legalistic. |
51 |
|
52 |
Yes, a computer program has to be pedantic and legalistic, because |
53 |
it has to follow the rules. You are instead working with an |
54 |
intentionally undefined notion of a "system" which you expect portage |
55 |
to magically protect, although you intentionally leave it completely |
56 |
unclear how portage should know what this system is. |
57 |
There are two ways how a computer program can know this: |
58 |
|
59 |
1. You tell it to the program. |
60 |
2. The program tries to smart-ass you by analyzing your configuration |
61 |
and boot-up files and makig some guesses about it. |
62 |
|
63 |
The solution 1 is the one chosen by gentoo. If you want 2, please use |
64 |
some of many other available distributions - and then learn how to |
65 |
workaround the problems if the program does the wrong guess in your |
66 |
case. |
67 |
|
68 |
> Quite simply |
69 |
> I expect that an OS, including Gentoo, will not delete itself unless |
70 |
> specifically asked by the user. I'm not getting involved in arguments |
71 |
> about details. |
72 |
|
73 |
THat's exactly your mistake: You cannot expect a program to do some |
74 |
vague unspecified things. (Except - see 2 above.) |
75 |
|
76 |
> Gentoo is not perfect. |
77 |
|
78 |
Nope. But the thing you complain about - the choice given to the user - |
79 |
is an *advantage* of gentoo. |
80 |
|
81 |
>> Oh, come on: You have misconfigured your system by making wrong |
82 |
>> assumptions, and now you call yourself the victim. |
83 |
> |
84 |
> I did not misconfigure my system. I followed the handbook |
85 |
|
86 |
No, you did not follow the handbook. The handbook says to put the |
87 |
packages you use into @world. Obviously, you did not. |
88 |
|
89 |
> I'm glad you're not the person responsible for safety in the place I |
90 |
> work. There, specific steps are taken to avoid injury to people who make |
91 |
> mistakes. For example, there are bars to prevent people from falling out |
92 |
> of windows, there are non-slip floor surfaces, and so on. |
93 |
|
94 |
Unix is nothing for you. It has no safety belts, and never can have |
95 |
without becoming something completely different. |
96 |
|
97 |
>> Probably everybody should know that practically *every* package |
98 |
>> can be a critical system file - it all depends on your setup. |
99 |
> |
100 |
> Please don't be like that. You know damn well that only a few packages |
101 |
> are critical |
102 |
|
103 |
Yes. But *which* ones are depends on your setup. |
104 |
Again, there are only the two possibilities: |
105 |
|
106 |
1. You are responsible for your system - and in particular tell portage |
107 |
what your system actually is. |
108 |
2. Portage is responsible for your system - then you have to be taken |
109 |
away any important choice about your main system, or portage tries to |
110 |
smart-ass you. |
111 |
|
112 |
Again, if you want 2, go to another distribution. For gentoo, 2 would |
113 |
be the death. |
114 |
|
115 |
> The init system is absolutely needed for *every* system. That there are |
116 |
> alternatives is no excuse for Gentoo to delete it. |
117 |
|
118 |
But not *all* installed init systems are absolutely needed for *every* system. |
119 |
There is no excuse for a "cleanup" command to not remove most of them, only |
120 |
because some guy *might* have configured only one of them. |
121 |
|
122 |
>> > Any system that comes within one keypress of destruction, when the user |
123 |
>> > hasn't specifically requested it, is a buggy system. portage is buggy. |
124 |
> |
125 |
>> alias ls="rm -rf /*" |
126 |
>> ls |
127 |
> |
128 |
> Don't be so silly, please. |
129 |
|
130 |
It is not more silly than your calling of portage buggy, only because it |
131 |
does not read your mind. |
132 |
|
133 |
>> Again, that the package is critical for *your* setup is a |
134 |
>> particularity of *your* system. |
135 |
> |
136 |
> The init system is critical to every system, even yours. |
137 |
|
138 |
Yes. But not necessarily openrc. And portage *cannot* know that openrc |
139 |
is critical for *your* setup. |
140 |
|
141 |
> I think our discussion has come to its natural end. |
142 |
|
143 |
Indeed, you want emerge to behave as "do what I mean" instead of |
144 |
"do what I tell you". The former is impossible for any computer program, |
145 |
in principle, and any further discussion about it gets void. |