From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update to /etc/sudoers disables wheel users!!!
Date: Wed, 26 Oct 2022 07:31:04 -0400 [thread overview]
Message-ID: <CAGfcS_mfrEQZwqimZ_K7JNSUk-g+3AqM2OHqzpe5Wr=ha8mpQQ@mail.gmail.com> (raw)
In-Reply-To: <AM6PR10MB244018D45D67CF1633EAB4F6EF309@AM6PR10MB2440.EURPRD10.PROD.OUTLOOK.COM>
On Wed, Oct 26, 2022 at 3:42 AM Ramon Fischer <Ramon_Fischer@hotmail.de> wrote:
>
> I do not know, what the developers were thinking to encourage the user
> to edit a default file, which gets potentially overwritten after each
> package update...
>
> "etc-update" helps to have an eye on, but muscle memory and fast fingers
> are sometimes faster.
The Gentoo preference tends to be to follow upstream. So if sudo
upstream distributes a file like this that has comments encouraging
users to edit it, then that is likely how Gentoo will ship it. If
sudo switched to moving everything into an include-based system
UPSTREAM then Gentoo would probably start shipping that. If you look
at the sudo ebuild you'll see that the config files are 100% upstream.
If you look at things like systemd units or udev rules they're much
more include-oriented, as this is the upstream preference.
Gentoo has emphasized using config file protection early on, and
doesn't have any official preference for using included config
directories distro-wide. Portage has been moving in this direction
for a while though (for the stuff in /etc/portage).
--
Rich
next prev parent reply other threads:[~2022-10-26 11:31 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 2:34 [gentoo-user] Update to /etc/sudoers disables wheel users!!! Walter Dnes
2022-10-26 3:04 ` Ramon Fischer
2022-10-26 3:15 ` Grant Taylor
2022-10-26 3:34 ` Ramon Fischer
2022-10-26 3:40 ` Ramon Fischer
2022-10-26 3:44 ` Matt Connell
2022-10-26 16:21 ` Grant Taylor
2022-10-26 17:15 ` Neil Bothwick
2022-10-26 17:31 ` Rich Freeman
2022-10-26 20:17 ` Dale
2022-10-26 21:26 ` [gentoo-user] " Grant Edwards
2022-10-26 22:44 ` Dale
2022-10-27 1:23 ` Ramon Fischer
2022-10-27 3:01 ` Dale
2022-10-27 7:55 ` Ramon Fischer
2022-10-27 7:59 ` Ramon Fischer
2022-10-26 23:55 ` Rich Freeman
2022-10-26 6:31 ` [gentoo-user] " Walter Dnes
2022-10-26 7:42 ` Ramon Fischer
2022-10-26 11:31 ` Rich Freeman [this message]
2022-10-26 14:41 ` Ramon Fischer
2022-10-26 16:52 ` Grant Taylor
2022-10-26 17:12 ` [gentoo-user] " Grant Edwards
2022-10-26 17:54 ` Ramon Fischer
2022-10-26 18:04 ` [gentoo-user] " Ramon Fischer
2022-10-26 18:22 ` Neil Bothwick
2022-10-26 19:28 ` Grant Taylor
2022-10-26 20:08 ` Neil Bothwick
2022-10-26 20:17 ` Grant Taylor
2022-10-26 21:13 ` Neil Bothwick
2022-10-26 21:29 ` Grant Taylor
2022-10-26 21:48 ` Ramon Fischer
2022-10-26 23:06 ` Grant Taylor
2022-10-27 1:27 ` Ramon Fischer
2022-10-27 1:47 ` Grant Taylor
2022-10-27 7:53 ` Ramon Fischer
2022-10-26 18:35 ` Jack
2022-10-26 18:38 ` Ramon Fischer
2022-10-26 20:06 ` Neil Bothwick
2022-10-26 21:27 ` Ramon Fischer
2022-10-26 21:30 ` Grant Taylor
2022-10-26 19:31 ` Grant Taylor
2022-10-26 19:26 ` Grant Taylor
2022-10-26 18:04 ` Ramon Fischer
2022-10-26 16:38 ` Grant Taylor
2022-10-26 3:12 ` Matt Connell
2022-10-26 4:00 ` Anna “CyberTailor”
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_mfrEQZwqimZ_K7JNSUk-g+3AqM2OHqzpe5Wr=ha8mpQQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox