all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: Wheel group as polkit admins
Date: Sat, 23 Nov 2019 18:17:59 +0100	[thread overview]
Message-ID: <87imna4im0.fsf@gnu.org> (raw)
In-Reply-To: <329f03fbb1df8c78deaef37c06c5041b3504c15e.camel@student.tugraz.at> (Leo Prikler's message of "Sun, 17 Nov 2019 18:52:07 +0100")

Hi Leo,

Leo Prikler <leo.prikler@student.tugraz.at> skribis:

> Thanks for the hint.  Since it's all just static text, I don't really
> need the whole Guile power of computed-file, so I've shortened it to:
>
> (define polkit-wheel
>   (file-union
>    "polkit-wheel"
>    `(("share/polkit-1/rules.d/wheel.rules"
>       ,(plain-file
>         "wheel.rules"
>         "polkit.addAdminRule(function(action, subject) {
>     return [\"unix-group:wheel\"];
> });
> ")))))

Neat.

>> Should we make that the default, BTW?  It would seem to make sense as
>> that’s the whole point of the “wheel” group.
>> 
>> What do people think?
>
> I'm probably biased as the author of this service, but I think it would
> probably make sense to include it in %desktop-services.  Perhaps we
> could even add wheel.rules to polkit-service-type itself, although I'm
> somewhat conflicted on that, as one could not opt out.

Yeah, let’s make it a separate service like you did.

Could you send a patch that does that?

Thanks!

Ludo’.

  reply	other threads:[~2019-11-23 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09 14:40 Wheel group as polkit admins Leo Prikler
2019-11-17 16:46 ` Ludovic Courtès
2019-11-17 17:52   ` Leo Prikler
2019-11-23 17:17     ` Ludovic Courtès [this message]
2019-11-23 19:08       ` Leo Prikler
2019-11-26 10:17         ` Ludovic Courtès
2019-11-26 12:35           ` Leo Prikler
2019-11-30 22:51             ` Ludovic Courtès
2019-11-17 18:18   ` Marius Bakke

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=87imna4im0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.