unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Sturmfels via Guix-patches via <guix-patches@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: "Léo Le Bouter" <lle-bout@zaclys.net>,
	47181@debbugs.gnu.org, "Nicolò Balzarotti" <anothersms@gmail.com>
Subject: [bug#47181] Packaging python-soundfile for use in MediaGoblin
Date: Tue, 30 Mar 2021 17:20:31 +1100	[thread overview]
Message-ID: <87eefxqi1c.fsf@sturm.com.au> (raw)
In-Reply-To: <YFCt9d9eni+dBHdz@3900XT>

On Wed, 17 Mar 2021, Efraim Flashner wrote:

> On Tue, Mar 16, 2021 at 01:49:51PM +0100, Léo Le Bouter via Guix-patches via wrote:
>> 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.
>
> The package gets rebuilt each time so it is less likely with Guix.
> However, if you substitute libsndfile.so and the full text is
> libsndfile.so.0.0.23 (or something similar) then you'll still end up
> with /gnu/store/...libsndfile.../libsndfile.so.0.0.23.

Thanks Efraim, Léo and Nicolò for the info on .so links.

This patch is now waiting on updates to libsndfile in core-updates. I'll
post an updated patch when that's merged. For now, I've inlined this
into MediaGoblin's guix-env.scm so I can keep working on the packaging
there.

Regards,
Ben




  reply	other threads:[~2021-03-30  6:21 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
2021-03-16 13:09       ` Efraim Flashner
2021-03-30  6:20         ` Ben Sturmfels via Guix-patches via [this message]
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=87eefxqi1c.fsf@sturm.com.au \
    --to=guix-patches@gnu.org \
    --cc=47181@debbugs.gnu.org \
    --cc=anothersms@gmail.com \
    --cc=ben@sturm.com.au \
    --cc=efraim@flashner.co.il \
    --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).