From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-dev] [REVIEW v2 0/2] 2020-09-28-python-2-7-cleanup news item
Date: Mon, 28 Sep 2020 10:46:07 +0200 [thread overview]
Message-ID: <ublhqs300@gentoo.org> (raw)
In-Reply-To: <20200928064256.124822-1-mgorny@gentoo.org> ("Michał Górny"'s message of "Mon, 28 Sep 2020 08:42:54 +0200")
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
>>>>> On Mon, 28 Sep 2020, Michał Górny wrote:
> I've figured out a better solution than changing PYTHON_TARGETS and then
> revbumping the packages to have users upgrade (which may happen before
> they change PYTHON_TARGETS). Instead, I'll revbump these few packages
> and remove Python 2 in new revisions.
> The majority of users will get the py2-less versions on next @world
> upgrade, and the few that need renpy, old mongodb, old kodi... will stay
> at current revision. This involves some temporary duplication
> on version bumps but I don't think this will be major issue.
Do I understand this right, future version bumps will have two parallel
ebuild revisions (like r0 and r100) with only the lower revision
supporting Python 2.7? Tricky. :)
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2020-09-28 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 6:42 [gentoo-dev] [REVIEW v2 0/2] 2020-09-28-python-2-7-cleanup news item Michał Górny
2020-09-28 6:42 ` [gentoo-dev] [REVIEW v2 1/2] 2020-09-28-python-2-7-cleanup: add a new " Michał Górny
2020-09-28 6:42 ` [gentoo-dev] [REVIEW v2 2/2] 2020-02-07-python-2-7-eol: remove superseded " Michał Górny
2020-09-28 8:46 ` Ulrich Mueller [this message]
2020-09-28 9:05 ` [gentoo-dev] [REVIEW v2 0/2] 2020-09-28-python-2-7-cleanup " Michał Górny
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=ublhqs300@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=python@gentoo.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