unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 37931@debbugs.gnu.org
Subject: bug#37931: util-linux dependency on udev
Date: Wed, 06 Nov 2019 16:40:18 +0100	[thread overview]
Message-ID: <877e4d109p.fsf_-_@gnu.org> (raw)
In-Reply-To: <87mudcoomv.fsf@devup.no> (Marius Bakke's message of "Sun, 03 Nov 2019 18:28:40 +0100")

Hi,

Marius Bakke <mbakke@fastmail.com> skribis:

> I had a look at the lsblkd source code, and found that it has an
> optional dependency on udev:
>
> https://github.com/karelzak/util-linux/blob/ccafadb7c58865f73d209fcfc74483be96cdf64d/misc-utils/lsblk-properties.c
>
> I tried building util-linux with udev support, and got the same output
> you expected without needing root privileges:
>
> (define-public util-linux/udev
>   (package/inherit
>    util-linux
>    (name "util-linux-with-udev")
>    (inputs
>     `(("udev" ,eudev)
>       ,@(package-inputs util-linux)))))
>
> Now, eudev already depends on util-linux, so adding udev support to the
> regular 'util-linux' package would introduce a circular dependency.
>
> I'm not sure what the best approach here is.  We could add a
> 'util-linux-minimal' for use in package inputs, and/or add a
> udev-enabled variant to %base-packages.

I think the latter is fine and can be done right away on ‘master’.

WDYT?

Ludo’.

  reply	other threads:[~2019-11-06 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26  1:22 bug#37931: Cannot guix refresh -ru util-linux to get updated lsblk Bengt Richter
2019-10-28 22:29 ` Marius Bakke
2019-11-02 14:42   ` Bengt Richter
2019-11-03 17:28     ` Marius Bakke
2019-11-06 15:40       ` Ludovic Courtès [this message]
2019-11-06 22:39       ` Bengt Richter
2020-01-08 19:14         ` Marius Bakke

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=877e4d109p.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=37931@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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).