unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Alexander Asteroth <alexander.asteroth@h-brs.de>
Cc: guix-devel@gnu.org
Subject: Re: How to handle package udev rules?
Date: Sun, 12 Dec 2021 17:24:17 +0100	[thread overview]
Message-ID: <87k0g9kc93.fsf@nckx> (raw)
In-Reply-To: <878rwqf1s4.fsf@h-brs.de>

[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]

Alexander,

Alexander Asteroth 写道:
> The question now is, what is the correct guix-way to implement 
> this:

Not as complicated as you fear!

udev rules aren't special.  Just install them to the package's own 
<out>/lib/udev/rules.d directory.  If the build system tries to 
write to another package's output, see if it provides any options 
to change that, or patch it in the worst case.

> 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?

Guix System provides a ready-made udev-rules-service to gather up 
all desired udev rules and pass them to the running udev.  I think 
this is how it works:

  (operating-system
    […]
    (services
      (cons* […]
             (udev-rules-service 'projecteur
                                 projecteur)
             %base-services)))

‘Think’ because I do it differently in my own configurations.

> Or is there another way for a package to provide the udev rules 
> from a
> user-level install? 

If this means ‘can I use Guix's udev rules on a foreign 
distribution’: I'm not sure, but not out of the box.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2021-12-12 16:40 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 ` Γυψ
2021-12-12 16:24 ` Tobias Geerinckx-Rice [this message]
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=87k0g9kc93.fsf@nckx \
    --to=me@tobias.gr \
    --cc=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).