From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai.kang@windriver.com, openembedded-core@lists.openembedded.org,
Alexander Kanavin <alexander.kanavin@intel.com>
Subject: Re: [PATCH 10/10] vala: update vapigen-wrapper
Date: Sat, 29 Sep 2018 13:33:37 +0100 [thread overview]
Message-ID: <16cf316e0447025d4df7b76653b408350f236ced.camel@linuxfoundation.org> (raw)
In-Reply-To: <0b27127115cad5c47512fe6384898234a9bf53db.1538199671.git.kai.kang@windriver.com>
On Sat, 2018-09-29 at 13:43 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> gobject-introspection has changed installation paths of .gir files.
gobject-introspection has not changed. *We* have changed it.
This is basically why I really don't want to start messing with
upstream code like this as I'm guessing this will be the first of many
such problems.
Has anyone discussed the gobject-introspection gir path issue with
upstream? If data is arch specific, it shouldn't be going into datadir
but into libexec iirc. I'd like to understand the upstream response
before we start hacking around this in OE in a way which will generate
a ton of patches and incompatibility.
Cheers,
Richard
next prev parent reply other threads:[~2018-09-29 12:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 5:43 [PATCH v2 00/10] Fix multilib install conflicts kai.kang
2018-09-29 5:43 ` [PATCH 01/10] cups: fix multilib install file conflicts kai.kang
2018-09-29 5:43 ` [PATCH 02/10] bind: " kai.kang
2018-09-29 5:43 ` [PATCH 03/10] man-db: fix multilib install file conflict kai.kang
2018-09-29 12:44 ` Richard Purdie
2018-09-30 1:02 ` Kang Kai
2018-09-29 5:43 ` [PATCH 04/10] groff: fix multilib install file conflicts kai.kang
2018-09-29 5:43 ` [PATCH 05/10] nss: move create blank certificates to pkg_postinst kai.kang
2018-09-29 12:44 ` Richard Purdie
2018-10-02 15:29 ` Kang Kai
2018-10-02 15:53 ` richard.purdie
2018-10-02 16:33 ` Kang Kai
2018-10-11 7:55 ` Kang Kai
2018-09-29 5:43 ` [PATCH 06/10] libcheck: avoid multilib install file conflict kai.kang
2018-09-29 12:42 ` Richard Purdie
2018-09-30 1:03 ` Kang Kai
2018-09-29 5:43 ` [PATCH 07/10] opkg-utils/update-alternatives: not warn same priorities for multilib kai.kang
2018-09-29 12:40 ` Richard Purdie
2018-09-29 5:43 ` [PATCH 08/10] os-release: fix install file conflict " kai.kang
2018-09-29 12:37 ` Richard Purdie
2018-09-30 1:07 ` Kang Kai
2018-09-29 5:43 ` [PATCH 09/10] gobject-introspection: fix multilib install file conflicts kai.kang
2018-09-29 5:43 ` [PATCH 10/10] vala: update vapigen-wrapper kai.kang
2018-09-29 12:33 ` Richard Purdie [this message]
2018-09-30 1:26 ` Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2018-09-29 5:01 [PATCH 00/10] Fix multilib install conflicts kai.kang
2018-09-29 5:01 ` [PATCH 10/10] vala: update vapigen-wrapper kai.kang
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=16cf316e0447025d4df7b76653b408350f236ced.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@intel.com \
--cc=kai.kang@windriver.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