Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: dracut: depend on eudev
Date: Fri, 08 Nov 2019 04:52:44 +0100	[thread overview]
Message-ID: <20191108035244.OuZnDypFhvDpGvJAL3vO_kswNZA49CNNqyHNdfKyMtw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16098@inbox.vuxu.org>

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

New comment by zdtcd on void-packages repository

https://github.com/void-linux/void-packages/pull/16098#issuecomment-551373412

Comment:
On 2019-11-07 18:18:58 -0800, Daniel Kolesa wrote:
> `kpartx` is required by `90multipath` and `90dmraid` modules and is
> a hard dependency in both e.g. debian and the official rpm .spec
> file (plus it's rather tiny), `e2fsprogs` is a hard dep in debian
> but not in the .spec, it's used by multiple modules but i guess
> mostly optionally.

    $ cat /usr/lib/dracut/dracut.conf.d/*.conf
    #
    # Void Linux default settings for dracut.
    #
    # Don't edit this file, it will be overwritten on next update.
    #
    add_dracutmodules+=" drm "
    stdloglvl=4
    add_dracutmodules+=" resume "
    omit_dracutmodules+=" systemd "
    i18n_vars="/etc/rc.conf:KEYMAP,FONT,FONT_MAP,FONT_UNIMAP"

Our default settings for dracut doesn't include multipath and dmraid.
We haven't shipped multipathd, anyway.
The dracut.spec file also put kpartx in the Recommends for fedora and
rhel (or for anything not fedora and rhel, I'm not familiar with spec
grmmar).

But, I think adding kpartx isn't a big deal, since it's a tiny package.

But, if we're gonna add every binary that dracut is using to depends,
I don't think it's a good idea.

How about adding this patch instead:

```
 modules.d/90dmraid/module-setup.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/modules.d/90dmraid/module-setup.sh b/modules.d/90dmraid/module-setup.sh
index 797a58e5..8038899a 100755
--- a/modules.d/90dmraid/module-setup.sh
+++ b/modules.d/90dmraid/module-setup.sh
@@ -6,6 +6,7 @@ check() {
     # if we don't have dmraid installed on the host system, no point
     # in trying to support it in the initramfs.
     require_binaries dmraid || return 1
+    require_binaries kpartx || return 1
 
     [[ $hostonly ]] || [[ $mount_needs ]] && {
         for dev in "${!host_fs_types[@]}"; do
```

-- 
Danh


  parent reply	other threads:[~2019-11-08  3:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04  5:34 [PR PATCH] " voidlinux-github
2019-11-04 15:34 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-07 15:08 ` voidlinux-github
2019-11-07 15:08 ` voidlinux-github
2019-11-08  1:14 ` voidlinux-github
2019-11-08  1:22 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-08  1:23 ` voidlinux-github
2019-11-08  2:18 ` voidlinux-github
2019-11-08  3:52 ` voidlinux-github [this message]
2019-11-08  4:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-08  5:57 ` voidlinux-github
2019-11-08  6:00 ` voidlinux-github
2019-11-08  6:16 ` [PR PATCH] [Merged]: " voidlinux-github
2019-11-08  7:33 ` voidlinux-github

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=20191108035244.OuZnDypFhvDpGvJAL3vO_kswNZA49CNNqyHNdfKyMtw@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).