From: Simon Tournier <zimon.toutoune@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: 65925@debbugs.gnu.org
Subject: bug#65925: bluez or jack in the closure of python-ipython?
Date: Thu, 14 Sep 2023 12:05:19 +0200 [thread overview]
Message-ID: <87msxpdq8w.fsf@gmail.com> (raw)
In-Reply-To: <cucmsxp9nov.fsf@riseup.net>
Hi,
On Thu, 14 Sep 2023 at 10:11, Csepp <raingloom@riseup.net> wrote:
> Seem pretty self-explanatory:
> matplotlib has a GUI frontend (or even multiple frontends), one of them
> is based on WxWidgets, which pulls in SDL2, and Guix doesn't split SDL2
> like some other distros do, so all its dependencies get pulled in.
> In case you are not familiar with SDL(2), it's a portable "direct media
> layer", a library used for portable multimedia applications.
So could you explain why bluez is not in the closure python-matplotlib?
--8<---------------cut here---------------start------------->8---
$ guix size python-matplotlib | grep '/gnu/store/' | cut -f1 -d' ' | cut -f2- -d'-' | sort
bash-minimal-5.1.16
bash-static-5.1.16
bzip2-1.0.8
bzip2-1.0.8
expat-2.5.0
fontconfig-minimal-2.14.0
font-dejavu-2.37
freetype-2.13.0
gcc-11.3.0-lib
gdbm-1.23
glibc-2.35
libffi-3.4.4
libpng-1.6.37
libx11-1.8.1
libxau-1.0.10
libxcb-1.15
libxdmcp-1.1.3
libxft-2.3.4
libxrender-0.9.10
ncurses-6.2.20210619
openssl-3.0.8
python-3.10.7
python-matplotlib-3.5.2
qhull-2020.2
readline-8.1.2
sqlite-3.39.3
tcl-8.6.12
tk-8.6.12
xz-5.2.8
zlib-1.2.13
--8<---------------cut here---------------end--------------->8---
And then why it is in the closure of python-ipython?
And as I pointed, bluez is not in the closure of any dependencies of
python-ipython.
Cheers,
simon
next prev parent reply other threads:[~2023-09-14 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 13:33 bug#65925: bluez or jack in the closure of python-ipython? Simon Tournier
2023-09-14 8:11 ` Csepp
2023-09-14 10:05 ` Simon Tournier [this message]
2023-09-15 10:06 ` Csepp
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=87msxpdq8w.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=65925@debbugs.gnu.org \
--cc=raingloom@riseup.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).