From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Partially revert "srcpkgs/*: remove all cryptocurrency/blockchain packages"
Date: Sun, 02 Jul 2023 13:24:38 +0200 [thread overview]
Message-ID: <20230702112438.VtAf2fy541LzE04bPNXIci3ub_DyhQiVsSnRAjUI7VA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44778@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
New comment by ar-jan on void-packages repository
https://github.com/void-linux/void-packages/pull/44778#issuecomment-1616610128
Comment:
I also really dislike how this was done. I actually understand that committers would prefer "no cryptocurrency" to not have to deal with this, but for existing packages that can't be the only consideration. There are users of these packages. The ones that were maintained could've been grandfathered in.
I hope we can get the Void Linux team to reconsider. If so, I'm willing to adopt `electrum`, I'd already been keeping that updated. I'd say not to keep `Electron-Cash`, since it requires a different libsecp256k library for full functionality, so it's better to run as AppImage.
next prev parent reply other threads:[~2023-07-02 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 23:05 [PR PATCH] " lemmi
2023-07-01 23:21 ` damadmai
2023-07-02 11:24 ` ar-jan [this message]
2023-07-02 22:00 ` Clos3y
2023-07-04 9:12 ` kevcrumb
2023-07-12 8:16 ` Clos3y
2023-07-19 9:09 ` lemmi
2023-07-19 10:32 ` ar-jan
2023-07-31 19:51 ` lemmi
2023-07-31 19:52 ` damadmai
2023-07-31 19:56 ` lemmi
2023-08-05 11:33 ` kevcrumb
2023-08-13 21:17 ` damadmai
2023-08-13 21:28 ` [PR REVIEW] " 0x5c
2023-08-26 8:02 ` sgn
2023-09-03 6:41 ` Yorizuka
2023-09-03 6:43 ` Yorizuka
2023-09-03 15:53 ` [PR PATCH] [Closed]: " lemmi
2023-10-17 20:44 ` wilkart
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=20230702112438.VtAf2fy541LzE04bPNXIci3ub_DyhQiVsSnRAjUI7VA@z \
--to=ar-jan@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).