From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] Harfbuzz bump major version question
Date: Mon, 20 Sep 2021 08:41:05 +0200 [thread overview]
Message-ID: <20210920084105.4b8fea91@windsurf> (raw)
In-Reply-To: <f98c560b-9a4f-26df-3bcb-3bdb4509786d@benettiengineering.com>
Hello Giulio,
On Sun, 19 Sep 2021 23:10:23 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> I'm going to bump harfbuzz to version 3.0.0 but being a major version it
> looses 15 apis[1] and introduce some new ones. So I'm not that sure if
> this can be a normal bump or I need to introduce the new package
> harfbuzz3. Package pango that requires harfbuzz builds fine, but how
> should I proceed? Should I build every package that depends on it and
> check if it builds fine? Or should I add package harfbuzz3 and then
> every package that depends on harfbuzz should move to harfbuzz3 package
> per package? I'm new to this case so help is appreciated.
The best is to not have to introduce a separate harfbuzz3 package, as
it really complicates things.
There are not that many packages that have a dependency on harfbuzz:
package/efl/efl.mk:ifeq ($(BR2_PACKAGE_HARFBUZZ),y)
package/libass/Config.in: select BR2_PACKAGE_HARFBUZZ
package/mupdf/Config.in: select BR2_PACKAGE_HARFBUZZ
package/pango/Config.in: select BR2_PACKAGE_HARFBUZZ
package/qt5/qt5base/Config.in:config BR2_PACKAGE_QT5BASE_HARFBUZZ
package/qt5/qt5base/Config.in: select BR2_PACKAGE_HARFBUZZ if \
package/qt5/qt5base/qt5base.mk:ifeq ($(BR2_PACKAGE_QT5BASE_HARFBUZZ),y)
package/supertuxkart/Config.in: select BR2_PACKAGE_HARFBUZZ
package/vlc/vlc.mk:ifeq ($(BR2_PACKAGE_HARFBUZZ),y)
package/webkitgtk/Config.in: select BR2_PACKAGE_HARFBUZZ
package/wpewebkit/Config.in: select BR2_PACKAGE_HARFBUZZ
So I would suggest to create a configuration that builds all those
packages successfully prior to the harfbuzz bump, and then retry this
configuration with the harfbuzz bump applied. This will give you a
sense of how much breakage the API changes are causing.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-20 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 21:10 [Buildroot] Harfbuzz bump major version question Giulio Benetti
2021-09-20 6:41 ` Thomas Petazzoni [this message]
2021-09-20 9:00 ` Arnout Vandecappelle
2021-09-20 11:15 ` Giulio Benetti
2021-09-20 11:11 ` Giulio Benetti
2021-09-20 19:12 ` [Buildroot] [PATCH] package/harfbuzz: bump to version 3.0.0 Giulio Benetti
2021-09-26 21:43 ` Arnout Vandecappelle
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=20210920084105.4b8fea91@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=yann.morin.1998@free.fr \
/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.