| 1 |
On Wed, 2021-08-04 at 14:35 +0200, Thomas Deutschmann wrote: |
| 2 |
> On 2021-08-04 04:56, Sam James wrote: |
| 3 |
> > Sure, thanks for the clarification. It's deprecated in the sense of |
| 4 |
> > ebuilds installing to it though, right? |
| 5 |
> |
| 6 |
> Well, it triggered me because saying it's deprecated implies two |
| 7 |
> things |
| 8 |
> for me: |
| 9 |
> |
| 10 |
> 1) It was OK for packages to do that in the past |
| 11 |
> |
| 12 |
> 2) Something has changed upstream |
| 13 |
> |
| 14 |
> Regarding 1) |
| 15 |
> It was never OK for packages to install in that location. That will |
| 16 |
> break the override mechanism systemd introduced. I.e. packages were |
| 17 |
> and |
| 18 |
> are still only allowed to install below /usr (/lib), to allow local |
| 19 |
> system administrators to override installed unit/tmpfiles spec by |
| 20 |
> placing a file with the same name in the corresponding directory in |
| 21 |
> /etc. |
| 22 |
> |
| 23 |
> |
| 24 |
> Regarding 2) |
| 25 |
> Nothing has changed upstream regarding these locations. |
| 26 |
> |
| 27 |
> |
| 28 |
> I personally hope that this QA check will never fire in hope we never |
| 29 |
> added an ebuild doing something like that but in the end, that's the |
| 30 |
> idea of having such a check: To notice something like that, just in |
| 31 |
> case ;-) |
| 32 |
|
| 33 |
So you've created a big commotion... because you didn't get the initial |
| 34 |
point? Honestly, this seems to be a recurring theme at this point. |
| 35 |
Someone suggests some improved check/some change, and nowadays you can |
| 36 |
bet 50 quid that Whissi will pop up and bikeshed it in some way. |
| 37 |
|
| 38 |
It's become a real problem at this point. In fact, we have proxy |
| 39 |
maintainers publicly refusing to work on packages somehow involving you |
| 40 |
(I'll mention no names, but check the #-desktop backlog), because your |
| 41 |
personality boils down to three attributes nowadays: |
| 42 |
|
| 43 |
1. If I say the sky is blue, you'll say it's green. If I say it's green, |
| 44 |
you'll say it's blue. I've had at least 5 people tell me they see the |
| 45 |
exact same pattern in you (and no, mgorny is not part of that set, |
| 46 |
before you throw that point at me). You're the textbook contrarian of |
| 47 |
Gentoo ("Wutbürger") right now. |
| 48 |
2. You'll tell people they are wrong, they aren't following protocols, |
| 49 |
they made a mistake, but you will never follow through with actually |
| 50 |
telling people what/why or how. By the time people ask you "why?", |
| 51 |
you've already disappeared. Given how frequently this happens in |
| 52 |
multiple channels, projects and at different time points, statistically, |
| 53 |
this can't be explained by coincidence any more. This happens |
| 54 |
practically on a daily basis, so you're not getting the benefit of the |
| 55 |
doubt any more. |
| 56 |
3. You can't let go. The security elections disaster right now is the |
| 57 |
prime example (yes, it's public, just check the history of the Security |
| 58 |
Project). This captures you so well: it's all about **community** and |
| 59 |
stuff, until you lose, then you start invoking technicalities and |
| 60 |
procedural shenanigans to justify some ludicrous kind of "co-lead" crap. |
| 61 |
Frankly, it's embarrassing, and you're at the centre of it. Instead of |
| 62 |
accepting defeat (remember, community and democracy!), you just fudge |
| 63 |
the results. |
| 64 |
|
| 65 |
At this point, you should really reflect on your current standing in |
| 66 |
Gentoo. I'm not saying this to disparage you, but to appeal to some kind |
| 67 |
of self-respect. |
Archives