From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Add plugdev to default groups, drop server_group in templates
Date: Thu, 07 Apr 2022 00:41:26 +0200 [thread overview]
Message-ID: <20220406224126.ZHzGNfVFtWIyw7RsvigFS0gN6lKGN3Lo_ZU8TACBqhk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36238@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
There's a merged pull request on the void-packages repository
Add plugdev to default groups, drop server_group in templates
https://github.com/void-linux/void-packages/pull/36238
Description:
Plugdev is used by many packages' udev rules for pluggable devices.
Currently, some of those packages use the system_groups trigger to add it, some forget to add it, and others patch it to "users" or "uaccess" (which breaks the packages on systems that don't use logind).
By adding plugdev to the default groups, we get rid of those problems.
This PR is needed for
- https://github.com/void-linux/void-packages/pull/34757
- https://github.com/void-linux/void-packages/pull/36144
While this pr deals with packages that had the `system_groups` hook to add plugdev, it does not deal with
1. packages that patch their rules to use `uaccess` instead (those packages are broken on systems that don't use logind)
I do not have the hardware to test any of those: `airspy hackrf libnfc openobex`
2. `libfido2`, which patches its rules to use `users`
This one works as is (I have hardware and I have to add myself to the `users` group to use it) but could arguably fit more in `plugdev`
#### Testing the changes
- I tested the changes in this PR: **YES** (base-files and openocd), **briefly** (I don't have hardware for openrazer or wally, but I did check that the removal of the hook was done correctly)
### **This PR will require addition of the plugdev group in the void documentation, PR: https://github.com/void-linux/void-docs/pull/663**
prev parent reply other threads:[~2022-04-06 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 3:31 [PR PATCH] Plugdev 0x5c
2022-03-20 4:55 ` [PR PATCH] [Updated] Add plugdev to default groups, drop server_group in templates 0x5c
2022-03-20 5:49 ` Anachron
2022-03-20 6:00 ` 0x5c
2022-03-29 10:03 ` [PR PATCH] [Updated] " 0x5c
2022-04-06 22:41 ` q66 [this message]
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=20220406224126.ZHzGNfVFtWIyw7RsvigFS0gN6lKGN3Lo_ZU8TACBqhk@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).