From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: "Ben Sturmfels" <ben@sturm.com.au>,
"Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 47181@debbugs.gnu.org
Subject: [bug#47181] Packaging python-soundfile for use in MediaGoblin
Date: Tue, 16 Mar 2021 13:49:51 +0100 [thread overview]
Message-ID: <fe84ee4badae4bd06c8298eb6e9cb18fc89f2daf.camel@zaclys.net> (raw)
In-Reply-To: <87ft0v1fs1.fsf@sturm.com.au>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
On Tue, 2021-03-16 at 22:47 +1100, Ben Sturmfels via Guix-patches via
wrote:
> Thanks, that solves my problem. One follow-up question - is it better
> to
> use the ".so" link or the specific "so.0"?
Use the more specific one since that is a symlink for a fixed ABI, if
the main library changes ABI it can then symlink with a bumped number
to indicate that and not break any dependent package. If you use the
less specific .so file directly then your package may suffer an ABI
break.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-16 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 3:50 [bug#47181] Packaging python-soundfile for use in MediaGoblin Ben Sturmfels via Guix-patches via
2021-03-16 7:51 ` Nicolò Balzarotti
2021-03-16 11:47 ` Ben Sturmfels via Guix-patches via
2021-03-16 12:44 ` Nicolò Balzarotti
2021-03-16 12:49 ` Léo Le Bouter via Guix-patches via [this message]
2021-03-16 13:09 ` Efraim Flashner
2021-03-30 6:20 ` Ben Sturmfels via Guix-patches via
2021-09-12 2:14 ` bug#47181: " Ben Sturmfels 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe84ee4badae4bd06c8298eb6e9cb18fc89f2daf.camel@zaclys.net \
--to=guix-patches@gnu.org \
--cc=47181@debbugs.gnu.org \
--cc=anothersms@gmail.com \
--cc=ben@sturm.com.au \
--cc=lle-bout@zaclys.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).