From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
Zhang Xiao <xiao.zhang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/7] eudev: fix file conflict when multilib enabled
Date: Tue, 27 Mar 2018 13:37:38 +0300 [thread overview]
Message-ID: <88e3e4f3-e431-8629-192e-e5ddfc0f45bc@linux.intel.com> (raw)
In-Reply-To: <ae9c1af4-ee4d-99f4-7485-968b17bb6811@windriver.com>
On 03/26/2018 06:28 PM, Mark Hatle wrote:
> I want a multilib_exec that can be used to generate a wrapper. The recipe will
> have to pass in the name of what is being wrapped, and how to determine the
> correct 'default'. The scripting should handle everything else. Like
> multilib_header it needs to generate an identical script no matter when multilib
> it's called with, avoiding any potential file conflict during install -- and
> then an automatic rename of the underlying 'executable'... using the same logic
> as multilib_header.
Thanks. This does look like a project that Wind River should be driving,
possibly even as a separate layer (initially). Would be good to have a
proven solution merged, rather than something half-baked with newly
discovered issues popping up down the road.
Alex
next prev parent reply other threads:[~2018-03-27 10:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 9:12 [PATCH 1/7] eudev: fix file conflict when multilib enabled Zhang Xiao
2018-03-12 9:12 ` [PATCH 2/7] python3: " Zhang Xiao
2018-03-12 9:12 ` [PATCH 3/7] vala: " Zhang Xiao
2018-03-12 9:13 ` [PATCH 4/7] gobject-introspection: " Zhang Xiao
2018-03-12 9:13 ` [PATCH 5/7] cairo: " Zhang Xiao
2018-03-16 15:56 ` Burton, Ross
2018-03-12 9:13 ` [PATCH 6/7] xtrans: " Zhang Xiao
2018-03-16 15:55 ` Burton, Ross
2018-03-12 9:13 ` [PATCH 7/7] icu: " Zhang Xiao
2018-03-12 10:13 ` [PATCH 1/7] eudev: " Alexander Kanavin
2018-03-12 18:38 ` Mark Hatle
2018-03-12 18:55 ` Alexander Kanavin
2018-03-12 19:48 ` Mark Hatle
2018-03-13 10:19 ` Alexander Kanavin
2018-03-26 15:28 ` Mark Hatle
2018-03-27 10:37 ` Alexander Kanavin [this message]
2018-03-27 14:38 ` Mark Hatle
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=88e3e4f3-e431-8629-192e-e5ddfc0f45bc@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xiao.zhang@windriver.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