From: Leo Famulari <leo@famulari.name>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: 44276@debbugs.gnu.org
Subject: [bug#44276] [PATCH] gnu: Add python-simpleaudio.
Date: Wed, 28 Oct 2020 12:43:57 -0400 [thread overview]
Message-ID: <20201028164357.GA13269@jasmine.lan> (raw)
In-Reply-To: <20201028090810.21543-1-tanguy@bioneland.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Wed, Oct 28, 2020 at 10:08:10AM +0100, Tanguy Le Carrour wrote:
> * gnu/packages/python-xyz.scm (python-simpleaudio): New variable.
> + (native-inputs
> + `(("alsa-lib" ,alsa-lib)))
After taking a closer look at the inputs in the pydub package, I noticed
that alsa-lib is a native-input; native-inputs are typically used only
while building the package.
The built package keeps a reference to alsa-lib:
------
$ guix gc --references $(./pre-inst-env guix build --no-grafts python-simpleaudio) | grep alsa-lib
/gnu/store/zcjdb23gbhl0pcnvvm8rnlprkfl43cv5-alsa-lib-1.2.2
$ grep -r alsa-lib $(./pre-inst-env guix build --no-grafts python-simpleaudio)
Binary file /gnu/store/kaiww0wf6a7kqzrn9la681lmwmp2k26w-python-simpleaudio-1.0.4/lib/python3.8/site-packages/simpleaudio/_simpleaudio.cpython-38-x86_64-linux-gnu.so matches
------
Either the reference is used and should not be the "native alsa-lib" (in
terms of cross-compiling), or it's not used and we can remove the
reference after building. I think the first option is more likely.
Should I change it from a 'native-input' to an 'input'?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-28 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 9:08 [bug#44276] [PATCH] gnu: Add python-simpleaudio Tanguy Le Carrour
2020-10-28 16:32 ` Leo Famulari
2020-10-28 16:43 ` Leo Famulari [this message]
2020-10-29 8:30 ` Tanguy Le Carrour
2020-10-29 14:14 ` bug#44276: " Leo Famulari
2020-10-29 14:26 ` [bug#44276] " Tanguy Le Carrour
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=20201028164357.GA13269@jasmine.lan \
--to=leo@famulari.name \
--cc=44276@debbugs.gnu.org \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.