From: NeelChotai <NeelChotai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: OpenRGB-0.2
Date: Fri, 10 Jul 2020 02:29:49 +0200 [thread overview]
Message-ID: <20200710002949.6E4Nogl10wPqgoXzwzL1X9BIKz5UWC-s4iYElqsunWQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22588@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
New comment by NeelChotai on void-packages repository
https://github.com/void-linux/void-packages/pull/22588#issuecomment-656416434
Comment:
Compiles successfully and confirmed working on x86_64.
Version 0.2 used system groups to control RGB which has been superseded by the udev rules in master. If anyone else can test and ensure that OpenRGB works without root permissions, this is good to merge.
next prev parent reply other threads:[~2020-07-10 0:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22588@inbox.vuxu.org>
2020-07-09 20:01 ` Eluminae
2020-07-09 20:53 ` NeelChotai
2020-07-09 23:39 ` [PR PATCH] [Updated] " NeelChotai
2020-07-10 0:29 ` NeelChotai [this message]
2020-07-23 20:08 ` NeelChotai
2020-07-23 20:42 ` NeelChotai
2020-07-23 21:46 ` NeelChotai
2020-07-24 0:12 ` [PR PATCH] [Updated] " NeelChotai
2020-07-24 0:16 ` NeelChotai
2020-10-06 18:03 ` [PR PATCH] [Updated] New package: OpenRGB-0.3 NeelChotai
2020-10-06 18:03 ` NeelChotai
2020-10-06 18:05 ` [PR PATCH] [Updated] " NeelChotai
2020-10-15 10:28 ` New package: OpenRGB-0.4 Piraty
2020-10-15 10:29 ` Piraty
2020-12-14 17:03 ` [PR PATCH] [Updated] " NeelChotai
2020-12-14 18:11 ` [PR PATCH] [Updated] New package: OpenRGB-0.5 NeelChotai
2020-12-14 18:12 ` NeelChotai
2020-12-14 18:19 ` NeelChotai
2020-12-17 22:52 ` [PR REVIEW] New package: openrgb-0.5 Piraty
2020-12-17 22:53 ` [PR PATCH] [Closed]: " Piraty
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=20200710002949.6E4Nogl10wPqgoXzwzL1X9BIKz5UWC-s4iYElqsunWQ@z \
--to=neelchotai@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).