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:07:33 +0200 [thread overview]
Message-ID: <20230731200733.dJ2b1jF38cW5CSMYAnBnZy4T1gLuFai7i3SrrV2JuPg@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: 964 bytes --]
New comment by maciozo on void-packages repository
https://github.com/void-linux/void-packages/pull/44422#issuecomment-1659058433
Comment:
It would have been nice to have some community input on the matter. While some discussion may have happened on IRC, it's apparent that not all of us have the time to spend on there. I was thinking that perhaps some sort of e-mailed newsletter whenever breaking changes like this occur, but @lemmi's suggestion of including it as an install message would probably be easier to manage. That plus some time for an RFC, especially for such a contraversial change.
> I have never heard of any packages getting that treatment (may have happened but never heard of that), nor did anyone suggest doing that.
I seem to recall something like this happening with a PipeWire package recently (`pipewire-media-session`, or something like that?), that was replaced with something else, but still managed to break my audio stack.
next prev parent reply other threads:[~2023-07-31 20:07 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 [this message]
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
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=20230731200733.dJ2b1jF38cW5CSMYAnBnZy4T1gLuFai7i3SrrV2JuPg@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).