From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Solaar: update to 1.0.7
Date: Tue, 12 Oct 2021 12:53:24 +0200 [thread overview]
Message-ID: <20211012105324.r2OwquYHKHtHxTT3bSys-NAIjCXejtapMa_fmE6mmx8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33425@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
New review comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/33425#discussion_r726999940
Comment:
```suggestion
To use Solaar without root privileges, copy the file
/usr/share/solaar/udev-rules.d/42-logitech-unify-permissions.rules
into the directory /etc/udev/rules.d/ and reload udev rules.
```
I don't really think we need an install message---it adds noise that most people will just ignore during installation and upgrades, the rule file is installed where upstream puts it, and we generally expect people to read the documentation of packages they install---but if it will clear up some confusion, the suggested change presents the optional rule while also providing a hint about how to use Solaar without using the rule.
next prev parent reply other threads:[~2021-10-12 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 16:32 [PR PATCH] Solaar: update to 1.0.7, install udev rules NeelChotai
2021-10-09 0:52 ` ahesford
2021-10-09 15:46 ` NeelChotai
2021-10-12 9:38 ` [PR PATCH] [Updated] " NeelChotai
2021-10-12 9:39 ` Solaar: update to 1.0.7 NeelChotai
2021-10-12 10:53 ` ahesford [this message]
2021-10-12 11:04 ` [PR PATCH] [Updated] " NeelChotai
2021-10-12 11:04 ` [PR REVIEW] " NeelChotai
2021-10-12 11:12 ` ahesford
2021-10-12 13:04 ` [PR PATCH] [Updated] " NeelChotai
2021-10-12 13:05 ` NeelChotai
2021-10-12 13:22 ` [PR PATCH] [Merged]: " ahesford
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=20211012105324.r2OwquYHKHtHxTT3bSys-NAIjCXejtapMa_fmE6mmx8@z \
--to=ahesford@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).