Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] dependencies.sh: Check for a host python version >= 2.7
Date: Mon, 31 Dec 2018 15:27:39 +0100	[thread overview]
Message-ID: <20181231142739.GA21682@scaer> (raw)
In-Reply-To: <CAFSsvmpWuEcruH55C-93Ek9fb0JKfHvex4NY2arGCxG5LD68OQ@mail.gmail.com>

On 2018-12-18 11:13 -0500, Adam Duskett spake thusly:
> Hello;
> 
> On Mon, Dec 17, 2018 at 6:25 PM Arnout Vandecappelle <arnout@mind.be> wrote:
> >
> >
> >
> > On 17/12/2018 14:10, ratbert90 wrote:
> > > Hello Peter;
> > >
> > > I would question as to why we would do anything to support such an old version of
> >> Python that was EOLed over 5 years ago.  Heck, even 2.7 will be EOLed in 2020.
> > >
> > > Looking around, the only distribution that has 2.6 that still has any kind of support
> >> is CentOS6, and even that is in maintenance mode.
> >
> >  RHEL6 will be retired November 30, 2020. SLES11 also hase Python 2.6 and will
> > be retired 31 Mar 2022.

RHEL5 gets extended support until end of 2020, while RHEL6 gets extended
support until mid-2024.

You would be amazed how old stuff tend to stick around in entrerpise-y
context. ;-]

> >
> > > 2.7 is a safe bet in my opinion.
> >
> >  Indeed, because it can be installed both on RHEL6 and on SLES11.
> >
> >  However, IIUC, it is *not* possible to install python 2.7 as the *default*
> > python on these distros, because some scripts that are used in normal operation
> > don't work with python 2.7.
> In the case of RHEL; one can run: `source /opt/rh/python27/enable` which will
> add the appropriate paths for Python2.7 to be the default.
> 
> As far as SLES11 goes, I don't know how many people use it, but it has to be
> microscopic at this point.
> 
> > So, the test that you added to dependencies.sh is
> > probably too strict, because it checks that python -V gives at least 2.7...
> If one runs `source /opt/rh/python27/enable` in CentOS6, then running
> `python -V`
> will give 2.7.13.

Since there are practical workarounds for affected users, I'm fine that
we require pythhon-2.7 now.

Note that, if libglib2 does require a host pytrhon-2.7 and we are not
willing to change our own requirements, then we can always add
host-python to libglib2's dependencies. But, meh...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-12-31 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 23:27 [Buildroot] [PATCH v3 1/2] dependencies.sh: Check for a host python version >= 2.7 aduskett at gmail.com
2018-12-16 23:27 ` [Buildroot] [PATCH v3 2/2] prerequisite.txt: Bump python dependency to 2.7 aduskett at gmail.com
2019-02-04 12:24   ` Peter Korsgaard
2018-12-17  7:28 ` [Buildroot] [PATCH v3 1/2] dependencies.sh: Check for a host python version >= 2.7 Peter Seiderer
2018-12-17 13:10   ` ratbert90
2018-12-17 23:25     ` Arnout Vandecappelle
2018-12-18 16:13       ` Adam Duskett
2018-12-31 14:27         ` Yann E. MORIN [this message]
2019-02-04 12:19 ` Peter Korsgaard

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=20181231142739.GA21682@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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