| 1 |
On Wed, Aug 4, 2021 at 5:35 AM Thomas Deutschmann <whissi@g.o> wrote: |
| 2 |
> |
| 3 |
> On 2021-08-04 04:56, Sam James wrote: |
| 4 |
> > Sure, thanks for the clarification. It's deprecated in the sense of |
| 5 |
> > ebuilds installing to it though, right? |
| 6 |
> |
| 7 |
> Well, it triggered me because saying it's deprecated implies two 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 and |
| 17 |
> are still only allowed to install below /usr (/lib), to allow local |
| 18 |
> system administrators to override installed unit/tmpfiles spec by |
| 19 |
> placing a file with the same name in the corresponding directory in /etc. |
| 20 |
> |
| 21 |
> |
| 22 |
> Regarding 2) |
| 23 |
> Nothing has changed upstream regarding these locations. |
| 24 |
|
| 25 |
Maybe next time, just explain that the first time around? |
| 26 |
|
| 27 |
Your first email provides no actionable information and requires the |
| 28 |
other party to expend effort (and wait for a reply) to understand what |
| 29 |
you mean. |
Archives