| 1 |
On Wed, Oct 26, 2022 at 3:42 AM Ramon Fischer <Ramon_Fischer@×××××××.de> wrote: |
| 2 |
> |
| 3 |
> I do not know, what the developers were thinking to encourage the user |
| 4 |
> to edit a default file, which gets potentially overwritten after each |
| 5 |
> package update... |
| 6 |
> |
| 7 |
> "etc-update" helps to have an eye on, but muscle memory and fast fingers |
| 8 |
> are sometimes faster. |
| 9 |
|
| 10 |
The Gentoo preference tends to be to follow upstream. So if sudo |
| 11 |
upstream distributes a file like this that has comments encouraging |
| 12 |
users to edit it, then that is likely how Gentoo will ship it. If |
| 13 |
sudo switched to moving everything into an include-based system |
| 14 |
UPSTREAM then Gentoo would probably start shipping that. If you look |
| 15 |
at the sudo ebuild you'll see that the config files are 100% upstream. |
| 16 |
|
| 17 |
If you look at things like systemd units or udev rules they're much |
| 18 |
more include-oriented, as this is the upstream preference. |
| 19 |
|
| 20 |
Gentoo has emphasized using config file protection early on, and |
| 21 |
doesn't have any official preference for using included config |
| 22 |
directories distro-wide. Portage has been moving in this direction |
| 23 |
for a while though (for the stuff in /etc/portage). |
| 24 |
|
| 25 |
-- |
| 26 |
Rich |
Archives