All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python-pillow: bump to version 6.2.2/7.0.0
Date: Tue, 14 Jan 2020 09:15:26 +0100	[thread overview]
Message-ID: <20200114091526.126189da@windsurf> (raw)
In-Reply-To: <20200113222430.5157-1-angelo@amarulasolutions.com>

On Mon, 13 Jan 2020 23:24:30 +0100
Angelo Compagnucci <angelo.compagnucci@gmail.com> wrote:

> This patch bumps Pillow to version 7.0.0 for Python3 and version
> 6.2.2 for Python2.
> Different versions here are needed cause the latest 7.0.0 only
> supports Python3, while support for Python2 is available in 6.2.2.
> 
> It updates also the LICENSE hash due to copyright year update.
> 
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> ---
> I don't really know if this is the correct way to support two versions
> of the same package, please let me know.

If the latest version only supports Python 3.x, then only support this
version, and make it "depends on BR2_PACKAGE_PYTHON3". Python 2.x is
now considered deprecated by the upstream Python developers. I don't
think Buildroot should bother with keeping old Python modules around
just for the sake of Python 2.x compatibility.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-01-14  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 22:24 [Buildroot] [PATCH] package/python-pillow: bump to version 6.2.2/7.0.0 Angelo Compagnucci
2020-01-14  8:15 ` Thomas Petazzoni [this message]
2020-01-14 23:21   ` Arnout Vandecappelle
2020-01-19  8:39   ` 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=20200114091526.126189da@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.