From: Kang Kai <Kai.Kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alexander.kanavin@intel.com>
Subject: Re: [PATCH 10/10] vala: update vapigen-wrapper
Date: Sun, 30 Sep 2018 09:26:45 +0800 [thread overview]
Message-ID: <96996649-d973-4f3f-b608-b1161fb803f2@windriver.com> (raw)
In-Reply-To: <16cf316e0447025d4df7b76653b408350f236ced.camel@linuxfoundation.org>
On 2018年09月29日 20:33, Richard Purdie wrote:
> 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.
I have sent the patch to
https://gitlab.gnome.org/GNOME/gobject-introspection/merge_requests/63.
It seems
no objection but can't build pass for VS2017, so not merged yet.
--Kai
>
> Cheers,
>
> Richard
>
>
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2018-09-30 1:30 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
2018-09-30 1:26 ` Kang Kai [this message]
-- 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=96996649-d973-4f3f-b608-b1161fb803f2@windriver.com \
--to=kai.kang@windriver.com \
--cc=alexander.kanavin@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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