From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rdma-core: update to 44.0.
Date: Tue, 10 Jan 2023 15:43:51 +0100 [thread overview]
Message-ID: <20230110144351.JKtHxCc5oW5SoxiWSpdWTCAVC6shTPxed0cB2UGhP0k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40866@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/pull/40866#issuecomment-1377343991
Comment:
> 1. `libibmad` has been subsumed by `rdma-core`, not really "removed". This is an important distinction for people who might attempt partial updates.
I have been under the impression the unused package (no reverse dependencies) can be safely removed, but since some people might *need* `libibmad`, I see no harm to try and symlink it to `rdma-core`.
> 2\. Just dropping the template will still leave the old `libibmad` in repositories, which will stage the repos the next time `rdma-core` bumps the soname of `libibumad.so.3`. That would require manual cleanup, usually at the least opportune time.
libibmad and libibumad are two different libraries, Andrew.
Even if `libibumad`'s soname gets changed at some point, libibmad plays no role here.
**UPD**: based on the discussion in #xbps, `libibmad` apparently depends on `libibumad`. If it was merged as is, libibmad may become broken if `libibumad.so.3` is bumped at some point. I am guilty on this part.
prev parent reply other threads:[~2023-01-10 14:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 1:49 [PR PATCH] rdma-core: update to 43.0 kruceter
2022-12-02 3:57 ` classabbyamp
2022-12-02 19:26 ` [PR REVIEW] " ahesford
2022-12-02 19:29 ` ahesford
2022-12-02 19:35 ` [PR PATCH] [Updated] " kruceter
2022-12-02 19:38 ` kruceter
2022-12-02 19:51 ` kruceter
2022-12-02 19:51 ` [PR REVIEW] " kruceter
2022-12-02 19:52 ` kruceter
2022-12-05 14:55 ` [PR PATCH] [Updated] " kruceter
2022-12-21 19:32 ` kruceter
2022-12-26 3:22 ` kruceter
2023-01-02 3:19 ` kruceter
2023-01-06 12:29 ` [PR PATCH] [Closed]: rdma-core: update to 44.0 kruceter
2023-01-10 14:03 ` [PR PATCH] [Updated] " kruceter
2023-01-10 14:12 ` kruceter
2023-01-10 14:13 ` kruceter
2023-01-10 14:16 ` [PR PATCH] [Updated] " kruceter
2023-01-10 14:30 ` kruceter
2023-01-10 14:36 ` [PR PATCH] [Closed]: " ahesford
2023-01-10 14:43 ` kruceter [this message]
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=20230110144351.JKtHxCc5oW5SoxiWSpdWTCAVC6shTPxed0cB2UGhP0k@z \
--to=kruceter@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).