From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: remove qt5jsbackend package
Date: Tue, 24 Dec 2013 08:45:45 +0100 [thread overview]
Message-ID: <20131224084545.6163a49e@skate> (raw)
In-Reply-To: <1387866891-31546-1-git-send-email-fatih.asici@gmail.com>
Dear Fatih A??c?,
On Tue, 24 Dec 2013 08:34:51 +0200, Fatih A??c? wrote:
> Upstream did not release a new version of this package since it is
> superseded by the builtin qml engine found in new qt5declarative.
>
> Fixes: http://autobuild.buildroot.net/results/3861aa91e03154c7d20f4157f0c3a1fa14838af1/
>
> Signed-off-by: Fatih A??c? <fatih.asici@gmail.com>
> ---
> package/qt5/Config.in | 1 -
> package/qt5/qt5declarative/Config.in | 13 +++++--
> package/qt5/qt5declarative/qt5declarative.mk | 2 +-
> package/qt5/qt5graphicaleffects/Config.in | 5 ++-
> package/qt5/qt5jsbackend/Config.in | 19 ----------
> ...ackend-0001-dont-import-bz2-python-module.patch | 29 ----------------
> package/qt5/qt5jsbackend/qt5jsbackend.mk | 40 ----------------------
> package/qt5/qt5multimedia/Config.in | 5 ++-
> package/qt5/qt5quick1/Config.in | 5 ++-
> package/qt5/qt5quick1/qt5quick1.mk | 2 +-
> package/qt5/qt5quickcontrols/Config.in | 5 ++-
> 11 files changed, 20 insertions(+), 106 deletions(-)
> delete mode 100644 package/qt5/qt5jsbackend/Config.in
> delete mode 100644 package/qt5/qt5jsbackend/qt5jsbackend-0001-dont-import-bz2-python-module.patch
> delete mode 100644 package/qt5/qt5jsbackend/qt5jsbackend.mk
Do we need a Config.in.legacy symbol for the removal of qt5jsbackend?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-24 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 6:34 [Buildroot] [PATCH] qt5: remove qt5jsbackend package Fatih Aşıcı
2013-12-24 7:45 ` Thomas Petazzoni [this message]
2013-12-24 8:05 ` Fatih Aşıcı
2013-12-24 8:20 ` Thomas Petazzoni
2013-12-25 17:16 ` Thomas Petazzoni
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=20131224084545.6163a49e@skate \
--to=thomas.petazzoni@free-electrons.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.