From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs: update to 2.1.7.
Date: Sat, 03 Dec 2022 08:44:52 +0100 [thread overview]
Message-ID: <20221203074452.s5Zg01efQsmljJLJ-awGbQlhgcFHH36uQnjKXTJFxew@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40874@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/40874#issuecomment-1336106331
Comment:
Can we split:
```
/usr/lib/libnvpair.so.3 -> /usr/lib/libnvpair.so.3.0.0
/usr/lib/libuutil.so.3 -> /usr/lib/libuutil.so.3.0.0
/usr/lib/libzfs.so.4 -> /usr/lib/libzfs.so.4.1.0
/usr/lib/libzfs_core.so.3 -> /usr/lib/libzfs_core.so.3.0.0
/usr/lib/libzfsbootenv.so.1 -> /usr/lib/libzfsbootenv.so.1.0.0
/usr/lib/libzpool.so.5 -> /usr/lib/libzpool.so.5.0.0
```
and make `zfs-devel` and `zfs` depends on `libzfs`? building `pam_zfscrypt` pulls the whole `zfs` in is annoying because of building `dkms`.
next prev parent reply other threads:[~2022-12-03 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 2:43 [PR PATCH] " zdykstra
2022-12-03 7:44 ` sgn [this message]
2022-12-03 23:26 ` Vaelatern
2022-12-04 22:09 ` zdykstra
2022-12-07 1:53 ` [PR PATCH] [Updated] " sgn
2022-12-07 2:03 ` [PR PATCH] [Merged]: " Vaelatern
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=20221203074452.s5Zg01efQsmljJLJ-awGbQlhgcFHH36uQnjKXTJFxew@z \
--to=sgn@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).