From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: raid5atemyhomework@protonmail.com, 45403@debbugs.gnu.org
Subject: [bug#45403] [PATCH] gnu: zfs: Split into packages specific for each of our major supported kernel versions.
Date: Fri, 25 Dec 2020 05:09:44 +0100 [thread overview]
Message-ID: <87tusaa5mf.fsf@nckx> (raw)
In-Reply-To: <tQf2iU3qAf-98GzhlfpFdOqngdpcHiunJZYtvDXKOm0vw-1XVHIpAHR72XwU6MsfxE1tf2jt3IcTu1xA1Y00GzHtk_emUTTbyGms936YLq4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
Hullo RAIDperson!
Thanks for working to improve Guix's currently broken ZFS package!
raid5atemyhomework via Guix-patches via 写道:
> What it changes is that it compiles kernel modules for all
> guix-provided kernel versions that ZFS currently is rated to
> support,
However, I oppose this (and not because ‘rated’ sets off my
corpo-speak alarms :-). It makes your system.scm tedious to
maintain, especially if we'd do this for all modules (and why
not?).
Worse, there's no such thing as ‘a 5.10’ Linux module that loads
on ‘a 5.10’ Linux kernel. We still need an easy generic method to
build modules against their chosen kernel and configuration.
As your patch illustrates, that already exists:
> (define (make-linux-zfs linux-libre)
> (package
> (inherit zfs-base)
> (arguments
> `(#:linux ,linux-libre)
> ,@(package-arguments zfs-base))
It just belongs in your system.scm, not in Guix itself.
Kind regards,
T G-R
P.S.nitpick: unfortunately this breaks localisation and can't be
done:
> + (string-append (package-description zfs-base)
> + "
> +
> +This package is deprecated, use linux-VERSION-zfs packages
> instead."))))
Descriptions need to be simple self-contained strings, even if it
means duplicating entire paragraphs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-25 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 10:59 [bug#45403] [PATCH] gnu: zfs: Split into packages specific for each of our major supported kernel versions raid5atemyhomework via Guix-patches via
2020-12-24 20:41 ` Leo Famulari
2020-12-25 1:12 ` raid5atemyhomework via Guix-patches via
2020-12-25 4:09 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-01-04 13:58 ` Danny Milosavljevic
2021-01-04 15:49 ` raid5atemyhomework via Guix-patches via
2021-01-04 16:07 ` raid5atemyhomework via Guix-patches via
2021-01-04 16:32 ` raid5atemyhomework via Guix-patches via
2021-01-08 15:50 ` bug#45403: " raid5atemyhomework via Guix-patches via
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=87tusaa5mf.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=45403@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=raid5atemyhomework@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.