From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 18/19] webkitgtk: update to 2.14.1
Date: Fri, 21 Oct 2016 18:17:55 +0300 [thread overview]
Message-ID: <71a7dd79-4c72-5f9d-d401-82142dccd349@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYqYBvyYnkE2Mud6DykHxbhD0ORvKCa7kUAZLfKqy_zog@mail.gmail.com>
On 10/20/2016 12:27 PM, Burton, Ross wrote:
> I should have finished reading the report before hitting send:
>
> packages/corei7-64-poky-linux/webkitgtk/webkitgtk: FILELIST: removed
> "/usr/lib/libwebkit2gtk-4.0.so.37.13.11
> /usr/lib/libjavascriptcoregtk-4.0.so.18.3.13" added
> "/usr/lib/libjavascriptcoregtk-4.0.so.18.4.8
> /usr/libexec/webkit2gtk-4.0/MiniBrowser /usr/libexec/webkit2gtk-4.0/jsc
> /usr/lib/libwebkit2gtk-4.0.so.37.14.8"
>
> If libexecdir is the right place for these then we can remove
> lib_package, otherwise the question is why are they in there and can
> they be moved back to bindir.
They did it on purpose, no idea why:
What's new in WebKitGTK+ 2.14.1?
- MiniBrowser and jsc binaries are now installed in pkglibexecdir
instead of bindir.
I've dropped the lib_package.
Alex
next prev parent reply other threads:[~2016-10-21 15:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 15:06 [PATCH 00/19] Recipe updates and version check fixes Alexander Kanavin
2016-10-19 15:06 ` [PATCH 01/19] musl: enable gobject introspection Alexander Kanavin
2016-10-19 15:06 ` [PATCH 02/19] mklibs-native: fix upstream version check Alexander Kanavin
2016-10-19 15:06 ` [PATCH 03/19] cve-check-tool: " Alexander Kanavin
2016-10-19 15:06 ` [PATCH 04/19] pigz: " Alexander Kanavin
2016-10-19 15:06 ` [PATCH 05/19] boost: update to 1.62.0 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 06/19] btrfs-tools: update to 4.8.1 Alexander Kanavin
2016-10-20 18:39 ` Burton, Ross
2016-10-24 13:02 ` Alexander Kanavin
2016-10-19 15:06 ` [PATCH 07/19] cmake: update to 3.6.2 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 08/19] dtc: update to 1.4.2 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 09/19] ffmpeg: update to 3.1.4 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 10/19] gnome-desktop3: update to 3.22.1 Alexander Kanavin
2016-10-20 9:24 ` Burton, Ross
2016-10-21 15:04 ` Alexander Kanavin
2016-10-19 15:06 ` [PATCH 11/19] gnutls: update to 3.5.5 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 12/19] libksba: update to 1.3.5 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 13/19] lighttpd: update to 1.4.42 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 14/19] mpg123: update to 1.23.8 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 15/19] nspr: update to 4.13 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 16/19] nss: update to 3.27.1 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 17/19] vala: update to 0.34.1 Alexander Kanavin
2016-10-19 15:06 ` [PATCH 18/19] webkitgtk: update to 2.14.1 Alexander Kanavin
2016-10-20 9:23 ` Burton, Ross
2016-10-20 9:27 ` Burton, Ross
2016-10-21 15:17 ` Alexander Kanavin [this message]
2016-10-19 15:06 ` [PATCH 19/19] epiphany: update to 3.22.1 Alexander Kanavin
2016-10-20 3:31 ` Khem Raj
2016-10-20 9:21 ` Alexander Kanavin
2016-10-19 19:42 ` [PATCH 00/19] Recipe updates and version check fixes akuster808
2016-10-20 9:16 ` Alexander Kanavin
2016-10-20 16:36 ` akuster808
2016-10-21 12:27 ` Alexander Kanavin
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=71a7dd79-4c72-5f9d-d401-82142dccd349@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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