[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VdsYVcPfgLUy5Gu=Q8t9zKyJ_=Ut0-__5WnxCjDhZQ-kA@mail.gmail.com>
Date: Thu, 24 Jun 2021 13:04:18 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Pavel Machek <pavel@....cz>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stable <stable@...r.kernel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Masahiro Yamada <masahiroy@...nel.org>
Subject: Re: [PATCH 4.19 425/425] scripts: switch explicitly to Python 3
On Wed, Jun 23, 2021 at 11:28 PM Pavel Machek <pavel@....cz> wrote:
> On Fri 2021-05-21 06:37:00, Greg Kroah-Hartman wrote:
> > On Fri, May 21, 2021 at 06:36:18AM +0200, Greg Kroah-Hartman wrote:
> > > On Thu, May 20, 2021 at 10:36:26PM +0200, Pavel Machek wrote:
...
> > > > Old distributions may not have python3 installed, and we should not
> > > > change this dependency in the middle of the series.
> > >
> > > What distro that was released in 2017 (the year 4.14.0 was released) did
> > > not have python3 on it?
> >
> > oops, I meant 2018, when 4.19.0 was out, wrong tree...
>
> In anything yocto-based, for example, you explicitely select which
> packages you want. And changing dependencies in middle of stable
> release is surprising and against our documentation.
How is this all relevant?
Scripts where the interpreter changed are not supposed to be used
outside of the (kernel) development process. No user should really
rely on those scripts to produce anything at any point of time or even
be there.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists