From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] directfb: bumping version to 1.6.3
Date: Sun, 10 Mar 2013 11:32:24 +0100 [thread overview]
Message-ID: <20130310113224.4e3dbb2a@skate> (raw)
In-Reply-To: <1362908858-6340-2-git-send-email-c.schoenert@gmail.com>
Dear Carsten Schoenert,
On Sun, 10 Mar 2013 10:47:35 +0100, Carsten Schoenert wrote:
> -DIRECTFB_VERSION_MAJOR = 1.4
> -DIRECTFB_VERSION = $(DIRECTFB_VERSION_MAJOR).17
> +DIRECTFB_VERSION_MAJOR = 1.6
> +DIRECTFB_VERSION = $(DIRECTFB_VERSION_MAJOR).3
> DIRECTFB_SITE = http://www.directfb.org/downloads/Core/DirectFB-$(DIRECTFB_VERSION_MAJOR)
> DIRECTFB_SOURCE = DirectFB-$(DIRECTFB_VERSION).tar.gz
> DIRECTFB_LICENSE = LGPLv2.1+
This looks good. However, we have a number of packages that depend or
can use DirectFB: cairo, directfb-examples, libecore, libevas, libgtk2,
links, lite, gst-plugins-bad, opencv, qt, sawman, sdl, webkit. Did you
test if those still build after this DirectFB bump? I have no idea if
the DirectFB bump from 1.4.x to 1.6.x is a major bump (like with API
breakage) or a minor bump. Depending on that, some testing of the
packages using DirectFB would be needed, or not.
Note that we don't necessarily require all those packages to continue
to build with DirectFB 1.6.x: if those packages haven't adapted to the
new DirectFB versions, then it's an upstream problem. However, if some
of those packages don't build, it would be good to update their
Config.in to ensure that the DirectFB variant is no longer offered/used.
Also, do just a reasonable amount of testing: our autobuilders will
anyway do a global testing of many combinations. But it's good to at
least check a few packages. If they work fine with the DirectFB bump,
then it's a good indication that the DirectFB bump probably didn't
introduce too much API breakage.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-10 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 9:47 [Buildroot] [PATCH 0/0] Updating directfb and divine Carsten Schoenert
2013-03-10 9:47 ` [Buildroot] [PATCH 1/4] directfb: bumping version to 1.6.3 Carsten Schoenert
2013-03-10 10:32 ` Thomas Petazzoni [this message]
2013-03-10 12:34 ` Carsten Schoenert
2013-03-17 13:59 ` Carsten Schoenert
2013-03-21 6:56 ` Arnout Vandecappelle
2013-03-21 18:06 ` Carsten Schoenert
2013-03-21 19:13 ` Thomas Petazzoni
2013-04-02 21:56 ` Carsten Schoenert
2013-03-10 16:50 ` Carsten Schoenert
2013-03-10 17:25 ` Thomas Petazzoni
2013-03-10 9:47 ` [Buildroot] [PATCH 2/4] divine: " Carsten Schoenert
2013-03-10 9:47 ` [Buildroot] [PATCH 3/4] directfb: expanding the help strings Carsten Schoenert
2013-03-10 10:27 ` Thomas Petazzoni
2013-03-10 12:21 ` Carsten Schoenert
2013-03-10 13:13 ` Thomas Petazzoni
2013-03-10 9:47 ` [Buildroot] [PATCH 4/4] directfb: fixing typo in variables Carsten Schoenert
2013-03-10 10:25 ` Thomas Petazzoni
2013-03-10 12:23 ` Carsten Schoenert
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=20130310113224.4e3dbb2a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox