From: Γυψ <gyps@member.fsf.org>
To: guix-devel@gnu.org
Subject: How to handle package udev rules?
Date: Sun, 12 Dec 2021 14:57:36 +0100 [thread overview]
Message-ID: <874k7dgbw1.fsf@member.fsf.org> (raw)
In-Reply-To: 878rwqf1s4.fsf@h-brs.de
Sorry, I sent this email from a non-subscribed account and therefore it
probably wasn't sent (if you receive it twice sorry for that).
Dear all,
I'm trying to build my first guix package and so far, after a lot of
trial and error to find the right packages providing the necessary cmake
functionality I managed to get the package to compile. (up to the point
where the install script want's to copy some udev rules file)
The package is a linux software that can be used with logitech
presenters [0]. Therefore it needs udev rules/devices to communicate
with the device.
The question now is, what is the correct guix-way to implement this:
I tried to import the libgudev module but that that only results in the
package wanting to write to another write-protected directory from the
store.
As I understand, the udev-rules are usually created on system
level. That would mean I need to split the package into a service part
and a package part? And remove the installation of the udev-file from
the package install process?
Or is there another way for a package to provide the udev rules from a
user-level install?
Cheers,
Alex
-----
[0] https://github.com/jahnf/Projecteur
next prev parent reply other threads:[~2021-12-12 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 12:12 How to handle package udev rules? Alexander Asteroth
2021-12-12 13:57 ` Γυψ [this message]
2021-12-12 16:24 ` Tobias Geerinckx-Rice
2021-12-12 18:17 ` Danny Milosavljevic
2021-12-12 20:58 ` gyps
2021-12-12 22:37 ` Danny Milosavljevic
2021-12-13 8:48 ` Γυψ
2021-12-17 8:20 ` Alexander Asteroth
2021-12-17 9:08 ` Josselin Poiret via Development of GNU Guix and the GNU System distribution.
2022-01-04 22:38 ` SeerLite
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=874k7dgbw1.fsf@member.fsf.org \
--to=gyps@member.fsf.org \
--cc=guix-devel@gnu.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.
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.