From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Python 3 restore alternatives
Date: Thu, 15 Oct 2020 18:44:00 +0200 [thread overview]
Message-ID: <20201015164400.TxJGxxJoE6tBxTod3Y6If9hnWezizPrvOi03hnUIUZE@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: 729 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/25583#issuecomment-709451263
Comment:
> @sgn if you want to make this smoother, just provide transitional packages to python3 variants,
I don't really like the transitional packages for this case, provides a fake update to remove things is not nice, and `python-foo` that depends on `python3-foo` makes even less sense.
> but i think keeping the conflicts is fine, it requires manual intervention from the user but also is relatively obvious
This was my line of thinking when I added the conflicts. I strongly prefer to keep the conflicts (since without `conflicts` tag, I see enough file conflict in other packages).
next prev parent reply other threads:[~2020-10-15 16:44 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
2020-10-15 16:44 ` sgn [this message]
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=20201015164400.TxJGxxJoE6tBxTod3Y6If9hnWezizPrvOi03hnUIUZE@z \
--to=sgn@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).