From: maciozo <maciozo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: srcpkgs/*: remove all cryptocurrency/blockchain packages
Date: Mon, 31 Jul 2023 22:36:28 +0200 [thread overview]
Message-ID: <20230731203628.MRXw-q3v-dxK5FBqk57lYQUAjsrsjrJlnqfZM5hiQ_4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44422@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
New comment by maciozo on void-packages repository
https://github.com/void-linux/void-packages/pull/44422#issuecomment-1659126343
Comment:
>At least from changes I've seen, I can name https://github.com/void-linux/void-packages/pull/40044 (PolyMC) as a package deemed undesirable (in that case, rogue upstream) with a then active userbase that also didn't get a message when removed despite the replacement being a not fully compatible fork.
That doesn't seem like a particularly desirable precedent to me. At least in that case the package was somewhat transparently replaced with a fork, and the reasoning for it had some merit. Here, packages are just being unilaterally removed from people's PCs with no warning and no alternative offered, for what seem to be somewhat opinionated reasons.
I get that Void isn't exactly meant to be a begginer-friendly distro, but I'm sure there are users out there who just blindly run `xi -Syu`, reasonably assuming that the OS won't suddenly remove potentially important software from their PCs.
next prev parent reply other threads:[~2023-07-31 20:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 5:59 [PR PATCH] " 0x5c
2023-06-15 19:47 ` paper42
2023-06-16 8:39 ` [PR PATCH] [Updated] " 0x5c
2023-06-16 19:26 ` ar-jan
2023-06-19 1:06 ` [PR PATCH] [Updated] " 0x5c
2023-06-26 20:07 ` [PR PATCH] [Merged]: " leahneukirchen
2023-06-28 14:56 ` SpecialBomb
2023-06-28 17:28 ` lemmi
2023-06-30 11:41 ` kevcrumb
2023-07-16 9:59 ` drizzt
2023-07-30 8:06 ` uberscientist
2023-07-30 17:37 ` 0x5c
2023-07-31 16:39 ` maciozo
2023-07-31 16:42 ` maciozo
2023-07-31 19:49 ` lemmi
2023-07-31 20:00 ` 0x5c
2023-07-31 20:07 ` maciozo
2023-07-31 20:09 ` maciozo
2023-07-31 20:12 ` ar-jan
2023-07-31 20:21 ` 0x5c
2023-07-31 20:36 ` maciozo [this message]
2023-07-31 20:37 ` lemmi
2023-09-03 4:59 ` Yorizuka
2023-09-03 5:28 ` Yorizuka
2023-09-03 22:01 ` Yorizuka
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=20230731203628.MRXw-q3v-dxK5FBqk57lYQUAjsrsjrJlnqfZM5hiQ_4@z \
--to=maciozo@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).