unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Asteroth <alexander.asteroth@h-brs.de>
To: guix-devel@gnu.org
Subject: How to handle package udev rules?
Date: Sun, 12 Dec 2021 13:12:50 +0100	[thread overview]
Message-ID: <878rwqf1s4.fsf@h-brs.de> (raw)

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


             reply	other threads:[~2021-12-12 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 12:12 Alexander Asteroth [this message]
2021-12-12 13:57 ` How to handle package udev rules? Γυψ
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rwqf1s4.fsf@h-brs.de \
    --to=alexander.asteroth@h-brs.de \
    --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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).