From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/sudo: removed template config, added convenient 'sudo' group config options.
Date: Thu, 24 Oct 2019 10:17:27 +0200 [thread overview]
Message-ID: <20191024101727.7af5db84@windsurf> (raw)
In-Reply-To: <e97fd4a9-2d28-1d36-1ad3-9ae3c4486fd8@mind.be>
Hello,
On Thu, 24 Oct 2019 00:15:01 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> With just a few sub-options, it's not worth making an additional menu. Kconfig
> will indent the sub-options when they're conditional on the immediately
> preceding symbol, as is the case here. That's enough.
Agreed.
> > +config BR2_PACKAGE_SUDO_GROUP
> > + bool "add system group 'sudo'"
> > + help
> > + Create a convenient system group named 'sudo' for
> > + granting users sudo permissions.
> > +
> > +config BR2_PACKAGE_SUDO_GROUP_RULE
> > + bool "allow member of group 'sudo' to execute any command."
> > + select BR2_PACKAGE_SUDO_GROUP
> > + help
> > + Reinserts this rule from the /etc/sudoers configuration file:
> > +
> > + %sudo ALL=(ALL) ALL
>
> Does it really make sense to have separate options for these two aspects? If
> you add a sudo group, it's most likely because you have something like that in
> your sudoers file. Without this option, you'll anyway need a custom sudoers file
> so it's pretty much irrelevant what you have in it.
>
> In fact, does it make sense to have the sudo group optional to begin with?
I think we don't need any new option at all:
(1) Just create the sudo group unconditionally
(2) Leave the customization of the /etc/sudoers file to the user,
through an overlay/post-build script. We cannot add zillions of
options to customize all aspects of each package configuration.
> > +define SUDO_REMOVE_GARBAGE
>
> Please split this into two patches, because they're doing two separate,
> unrelated things. In fact, your commit message already suggests this because you
> say "this and that".
>
> Speaking of the commit message: it should use imperative (remove, add) and
> should not end with a dot (at least the summary line shouldn't).
Agreed. Also please don't use "garbage", I think we can find a better
word than garbage.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-24 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 21:14 [Buildroot] [PATCH 1/1] package/sudo: removed template config, added convenient 'sudo' group config options Stephan Henningsen
2019-10-23 22:15 ` Arnout Vandecappelle
2019-10-23 23:19 ` Stephan Henningsen
2019-10-24 8:17 ` Thomas Petazzoni [this message]
2019-10-24 21:26 ` Stephan Henningsen
2019-10-25 8:10 ` Arnout Vandecappelle
2019-10-25 8:15 ` Thomas Petazzoni
2019-10-25 19:20 ` Stephan Henningsen
-- strict thread matches above, loose matches on Subject: below --
2019-10-23 21:48 Stephan Henningsen
2019-10-23 21:50 Stephan Henningsen
2019-10-23 22:02 Stephan Henningsen
2019-10-23 22:03 Stephan Henningsen
2019-10-23 22:04 Stephan Henningsen
2019-10-23 22:05 Stephan Henningsen
2019-10-23 22:07 Stephan Henningsen
2019-10-23 22:11 Stephan Henningsen
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=20191024101727.7af5db84@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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