From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] For next council meeting: moving Portage to python3.6+
Date: Wed, 25 Apr 2018 04:50:59 -0700 [thread overview]
Message-ID: <CAGDaZ_oaxgnPLZ2Lry2ktPPFvpTjXezp60pdkt6i6uqtVcgTeQ@mail.gmail.com> (raw)
In-Reply-To: <4bcc5cdd719e05abe61ca8affab11c82@troglodyte.be>
On Wed, Apr 25, 2018 at 2:29 AM, <nado@troglodyte.be> wrote:
> April 25, 2018 8:56 AM, "Michał Górny" <mgorny@gentoo.org> wrote:
>
>> W dniu śro, 18.04.2018 o godzinie 08∶58 -0700, użytkownik Zac Medico
>> napisał:
>>
>> Removing support for Python 2.7 is going to be a major drawback for our
>> users. I am not even going to consider those who intentionally reduce
>> their systems to 2.7 only for one reason or another. However, 2.7 has
>> been the Gentoo's 'LTS' so far -- different versions of Python 3 come
>> and go but 2.7 was there for a very long time to ease the transition.
>> Only recently one of the developers had to solve hard upgrade conflicts
>> and the simplest way of doing that was to unmerge Python 3 and use
>> Python 2.7 to install a new version.
>
> I think that workaround is even more common when you have to update some really old install.
> I've experienced it two times with Gentoo over the last 5 years, first time was my fault, I messed
> up my system, and the other is for serously outdated scaleway images [1].
> It happens and I agree on keeping 2.7 support for a bit longer.
>
>> With EAPI 7 approaching in days (and the implementation going to
>> probably have some inevitable bugs), switching supported Python
>> implementation (or doing any major refactorings, to say) is a very bad
>> idea. This is going to once again cause a horrible backwards
>> compatibility problem loop where people wouldn't be able to use EAPI 7
>> because they would need to provide means to upgrade Python and its
>> dependencies first, in order to be able to upgrade Portage.
>
> I agree with this, I'd like to see changes coming nicely separated, not in a bunch and be left
> determining why I can't upgrade my old system anymore.
I might have misread this, but isn't it policy that Gentoo doesn't
support upgrades of systems more than a year old?
I think it was said that if you go a year without updating, you aren't
supported anymore and you need to just do a fresh install.
Does anyone have any commentary on this? Even to tell me that I'm mistaken?
>
> [1] https://github.com/scaleway/image-gentoo/issues/8#issuecomment-343210153
>
> --
> Corentin “Nado” Pazdera
>
prev parent reply other threads:[~2018-04-25 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 2:58 [gentoo-project] For next council meeting: moving Portage to python3.6+ Daniel Robbins
2018-02-24 4:42 ` [gentoo-project] " Benda Xu
2018-02-24 8:57 ` [gentoo-project] " Michał Górny
2018-02-24 17:55 ` R0b0t1
2018-02-24 19:45 ` Daniel Robbins
2018-02-24 19:50 ` M. J. Everitt
2018-02-24 19:57 ` Daniel Robbins
2018-02-24 20:06 ` M. J. Everitt
2018-02-24 20:44 ` R0b0t1
2018-04-18 15:58 ` Zac Medico
2018-04-25 6:56 ` Michał Górny
2018-04-25 9:42 ` Zac Medico
2018-04-25 9:29 ` nado
2018-04-25 11:50 ` Raymond Jennings [this message]
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=CAGDaZ_oaxgnPLZ2Lry2ktPPFvpTjXezp60pdkt6i6uqtVcgTeQ@mail.gmail.com \
--to=shentino@gmail.com \
--cc=gentoo-project@lists.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