From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sndio: update to 1.7.0
Date: Mon, 31 Aug 2020 22:49:02 +0200 [thread overview]
Message-ID: <20200831204902.e9kHqey3yIurrq_5TnK1vUq-1zW7BQcXETSJBbQTR3Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24581@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/24581#issuecomment-684029911
Comment:
Well its tricky, we have to rebuild, we could work around it with the patch I linked, but then our binaries would use different SONAMEs than everyone else (so you can't just build binaries linking against libsndio and run them on other distributions with the same version of sndio available, its not that bad in this case but is bad practice and might lead to more issues in the future, see ncurses and the libtinfo issues distributions run into).
Which is not optimal. I send out a patch to the sndio mailing list just now and I think its best to wait for feedback and then decide how to continue.
next prev parent reply other threads:[~2020-08-31 20:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 19:32 [PR PATCH] " archfan
2020-08-31 19:39 ` ericonr
2020-08-31 19:40 ` ericonr
2020-08-31 19:45 ` [PR PATCH] [Updated] " archfan
2020-08-31 19:48 ` archfan
2020-08-31 19:48 ` ericonr
2020-08-31 19:49 ` archfan
2020-08-31 19:50 ` ericonr
2020-08-31 20:00 ` [PR PATCH] [Updated] " archfan
2020-08-31 20:09 ` Duncaen
2020-08-31 20:10 ` Duncaen
2020-08-31 20:11 ` archfan
2020-08-31 20:12 ` Duncaen
2020-08-31 20:13 ` archfan
2020-08-31 20:22 ` Duncaen
2020-08-31 20:26 ` [PR PATCH] [Updated] " archfan
2020-08-31 20:38 ` [PR PATCH] [Closed]: " archfan
2020-08-31 20:38 ` [PR PATCH] [Updated] " archfan
2020-08-31 20:44 ` archfan
2020-08-31 20:44 ` archfan
2020-08-31 20:46 ` Duncaen
2020-08-31 20:46 ` Duncaen
2020-08-31 20:49 ` Duncaen [this message]
2020-09-02 15:05 ` [PR PATCH] [Closed]: " Duncaen
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=20200831204902.e9kHqey3yIurrq_5TnK1vUq-1zW7BQcXETSJBbQTR3Q@z \
--to=duncaen@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).