From: Vagrant Cascadian <vagrant@debian.org>
To: Guillaume Le Vaillant <glv@posteo.net>,
John Kehayias <john.kehayias@protonmail.com>
Cc: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Subject: python-ledgerblue as input for electrum? (was: Core-updates, the last metres)
Date: Sun, 23 Apr 2023 16:32:52 -0700 [thread overview]
Message-ID: <87wn22xjh7.fsf@contorta> (raw)
In-Reply-To: <871qkaicse.fsf@kitej>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On 2023-04-23, Guillaume Le Vaillant wrote:
> Here are a few leaf packages that don't build because of some
> failing dependencies:
> - blender is blocked by opencolorio
> - electrum is blocked by python-ledgerblue
Hrm this is kind of an aisde, but python-ledgerblue is a plugin for
electrum to support specific hardware, which makes me wonder why it is
in one of the inputs for electrum at all...
There is at least one other, python-btchip-python; electron-cash has
similar inputs, python-keepkey and python-trezor.
My understanding is optional plugins in general should not be in inputs
for packages; people should add the plugins to their profile or
manifest, etc. for the hardware they plan to use...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-04-23 23:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 7:30 Core-updates, the last metres Andreas Enge
2023-04-23 18:51 ` John Kehayias
2023-04-23 19:25 ` Andreas Enge
2023-04-23 20:00 ` Guillaume Le Vaillant
2023-04-23 21:12 ` John Kehayias
2023-04-24 10:00 ` Josselin Poiret
2023-04-24 10:01 ` [PATCH] gnu: python-shiboken-2: Do not rely on _Py_Mangle being available Josselin Poiret
2023-04-24 10:57 ` Andreas Enge
2023-04-23 23:32 ` Vagrant Cascadian [this message]
2023-04-23 23:45 ` python-ledgerblue as input for electrum? (was: Core-updates, the last metres) John Kehayias
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=87wn22xjh7.fsf@contorta \
--to=vagrant@debian.org \
--cc=andreas@enge.fr \
--cc=glv@posteo.net \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
/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.