Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Request] Distribute zfs module as package
Date: Thu, 15 Jul 2021 13:48:10 +0200	[thread overview]
Message-ID: <20210715114810.cT3M9W2gYrJbXblpl7ZEIXCC3yWB96EuonyjeaD9kVI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31629@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/31629#issuecomment-880629469

Comment:
I'm a heavy proponent of ZFS and have a stake in keeping first-class support in Void, but this isn't the answer. Any potential license issues aside, this is a bad idea because:
1. Void isn't set up to have module packages track the kernels directly. We use DKMS because we can't provide installable modules for whatever kernel version you might be running, because our kernel package may have already left you behind.
2. The workaround would be to build ZFS within the kernel package so that each package has the modules you need. However:
* This admits the possibility that ZFS kmods and user land tools get out of sync, which could eventually be catastrophic.
* This adds maintenance burden to the kernel packages, which are complicated enough already.
* This would require we rebuild all kernels for every ZFS bump or else live with out-of-sync kernel and user space components from the outset; both are unattractive.
* Pulling ZFS into the kernel package leads to "what-about" arguments where people start fighting about why their preferred kernel module isn't also precompiled.

I would love binary ZFS modules, especially when I make the mistake of updating the ZFS package without first vkpurging; watching ZFS build 6 times for kernels I want to throw away anyway is painful. Unfortunately, we aren't set up for this.

  parent reply	other threads:[~2021-07-15 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 15:37 [ISSUE] " Ypnose
2021-06-23 16:06 ` Vaelatern
2021-06-23 16:27 ` Ypnose
2021-07-12 19:03 ` Ypnose
2021-07-12 19:03 ` Ypnose
2021-07-12 19:14 ` q66
2021-07-13  4:09 ` Ypnose
2021-07-15 11:48 ` [ISSUE] [CLOSED] " ahesford
2021-07-15 11:48 ` ahesford [this message]
2021-07-17  6:36 ` Ypnose

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=20210715114810.cT3M9W2gYrJbXblpl7ZEIXCC3yWB96EuonyjeaD9kVI@z \
    --to=ahesford@users.noreply.github.com \
    --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).