From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 7/7] webkitgtk: update 2.38.5 -> 2.40.0
Date: Sat, 25 Mar 2023 20:38:33 +0100 [thread overview]
Message-ID: <98D3SR.ES0FR9UCE62O2@t-online.de> (raw)
In-Reply-To: <174FBE6FF0B9B09E.25304@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Am Sa, 25. Mär 2023 um 19:56:00 +0100 schrieb Markus Volk
<f_l_k@t-online.de>:
> webkitgtk-4 is confusing for the gtk3 variant, but named it anyway
> because meson reports that webkitgtk-4.0 is missing if it is not found
During the change I noticed that webkitgtk-4 (built with gtk3) also
stores its libs in ${libdir}/webkit2gtk-4.*. If I now rename the recipe
to webkitgtk-3, won't the confusion increase?
[-- Attachment #2: Type: text/html, Size: 517 bytes --]
next prev parent reply other threads:[~2023-03-26 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 0:48 [oe-core][PATCH 1/7] glib-2.0: update 2.74.6 -> 2.76.1 Markus Volk
2023-03-25 0:48 ` [oe-core][PATCH 3/7] glib-networking: update 2.74.0 -> 2.76.0 Markus Volk
2023-03-25 0:48 ` [oe-core][PATCH 4/7] gsettings-desktop-schemas: update 43.0 -> 44.0 Markus Volk
2023-03-25 0:48 ` [oe-core][PATCH 5/7] adwaita-icon-theme: update 43 " Markus Volk
2023-03-25 0:48 ` [oe-core][PATCH 6/7] epiphany: update 43.1 " Markus Volk
2023-03-27 14:38 ` Alexandre Belloni
2023-03-28 0:54 ` Markus Volk
2023-03-28 8:27 ` Alexander Kanavin
2023-03-28 13:33 ` Khem Raj
2023-03-28 13:45 ` Alexander Kanavin
2023-03-25 0:48 ` [oe-core][PATCH 7/7] webkitgtk: update 2.38.5 -> 2.40.0 Markus Volk
2023-03-25 18:35 ` Alexander Kanavin
2023-03-25 18:56 ` Markus Volk
[not found] ` <174FBE6FF0B9B09E.25304@lists.openembedded.org>
2023-03-25 19:38 ` Markus Volk [this message]
2023-03-26 16:57 ` Alexander Kanavin
2023-03-26 17:07 ` Markus Volk
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=98D3SR.ES0FR9UCE62O2@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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