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, 13 Mar 2018 12:19:16 +0200 [thread overview]
Message-ID: <4813fff9-6e19-4c8d-e22e-2ab6ce5e8989@linux.intel.com> (raw)
In-Reply-To: <cc14195a-81df-190f-23fa-9c914e21e6d9@windriver.com>
On 03/12/2018 09:48 PM, Mark Hatle wrote:
> Then an advanced user to select a specific version of the 'alternatives'. The
> key with all of this is that it needs to be 'reasonable' for both the recipe
> maintainer and the end user. Having to manually rename things, use the existing
> update-alternatives, etc really isn't a good idea -- even if it solves (some of)
> the user issues.
But what is the specific need for having both 32 and 64 bit development
packages *installed at the same time*? You do need to explain this,
because any solution will add complexity and headaches for oe-core
maintainers, and multilib is already far too complex and tricky.
If the customer is fine with switching between the two sets, then this
can be trivially solved using existing tools:
1. Deinstall 32 bit dev packages on device.
2. Install matching 64 bit dev packages on device
... or vice versa. Just wrap it in a script.
Alex
next prev parent reply other threads:[~2018-03-13 10:25 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 [this message]
2018-03-26 15:28 ` Mark Hatle
2018-03-27 10:37 ` Alexander Kanavin
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=4813fff9-6e19-4c8d-e22e-2ab6ce5e8989@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.