Github messages for voidlinux
 help / color / mirror / Atom feed
From: robertek <robertek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs: divide under subpackages
Date: Tue, 28 Feb 2023 17:44:36 +0100	[thread overview]
Message-ID: <20230228164436.sEpo_7Ds_EAjUxKoZ_3zQcu1n1lYoNZZUhBgsu4bnqs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42484@inbox.vuxu.org>

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

New comment by robertek on void-packages repository

https://github.com/void-linux/void-packages/pull/42484#issuecomment-1448505954

Comment:
I understand the intention to keep this as simple as possible from the maintenance point of view. I have also refactored it the way it would not interfere the stock users and allow customization if wanted. I definitely do not want to brake something in spite of some custom users.

I understand the noextract option, but wouldn't be viable just create subpackages for stuff that is able to be "noextracted" with nearly no cost? Or if it is some non-written convention in Void not to create subpackages much (as for example Alpine do) I would understand that.

Wouldn't then be an option to keep the zfs-userland in zfs package and only create subpackages with dkms and zed? The zfs-test is something that should not be present on any semi-production/user system anyway (but this is true also for the zinject).

With the version incompatibility breakage I remember that form the time of 0.6 versions myself, but since 2.0 or 2.1 I have never see any commit in 2.x branch to break the interoperability between kernel-useralnd on the same branch. And it is not an intention of this refactor. DKMS users will still have the same version on both and the ones that build the zfs inside kernel just need to care themselves.

  parent reply	other threads:[~2023-02-28 16:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 14:38 [PR PATCH] " robertek
2023-02-28 13:04 ` [PR REVIEW] " ahesford
2023-02-28 13:04 ` ahesford
2023-02-28 13:04 ` ahesford
2023-02-28 13:48 ` robertek
2023-02-28 13:49 ` ahesford
2023-02-28 13:50 ` robertek
2023-02-28 13:52 ` robertek
2023-02-28 13:53 ` ahesford
2023-02-28 14:05 ` robertek
2023-02-28 14:28 ` ahesford
2023-02-28 16:43 ` [PR PATCH] [Closed]: " Vaelatern
2023-02-28 16:43 ` Vaelatern
2023-02-28 16:44 ` robertek [this message]
2023-02-28 16:45 ` robertek

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=20230228164436.sEpo_7Ds_EAjUxKoZ_3zQcu1n1lYoNZZUhBgsu4bnqs@z \
    --to=robertek@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).