From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Python 3 restore alternatives
Date: Thu, 15 Oct 2020 18:28:36 +0200 [thread overview]
Message-ID: <20201015162836.KOhxch8aiMqf7F6jU-qlLCp62tfCYGkBVHvZg7fxicc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25583@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/25583#issuecomment-709442169
Comment:
@Chocimier i don't disagree that this is a non-ideal situation, but we probably shouldn't be doing stuff that actually creates a bigger mess while xbps still doesn't have any solution for this
also, i don't think the argument holds for python2 packages either way; python2 is on its way out, and arguing with "disrupting users' workflows" is pointless since sooner or later these packages will create conflicts with other stuff in the system (well, they already are, which is the point of this PR in the first place)
@sgn if you want to make this smoother, just provide transitional packages to python3 variants, but i think keeping the conflicts is fine, it requires manual intervention from the user but also is relatively obvious
next prev parent reply other threads:[~2020-10-15 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 0:21 [PR PATCH] " sgn
2020-10-15 2:12 ` ahesford
2020-10-15 2:19 ` q66
2020-10-15 2:42 ` ahesford
2020-10-15 3:14 ` q66
2020-10-15 3:22 ` ahesford
2020-10-15 3:54 ` q66
2020-10-15 6:39 ` Chocimier
2020-10-15 14:24 ` sgn
2020-10-15 16:28 ` q66 [this message]
2020-10-15 16:44 ` sgn
2020-10-15 16:55 ` Chocimier
2020-10-18 14:42 ` sgn
2020-10-18 14:42 ` [PR PATCH] [Closed]: " sgn
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=20201015162836.KOhxch8aiMqf7F6jU-qlLCp62tfCYGkBVHvZg7fxicc@z \
--to=q66@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).