From: Mark Hatle <mark.hatle@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Kang Kai <Kai.Kang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] remove allarch from recipes which rdepends on TUNE_PKGARCH packages
Date: Tue, 7 Aug 2018 12:07:38 -0500 [thread overview]
Message-ID: <eaca6350-e83c-129a-20fa-1484dab18cf5@windriver.com> (raw)
In-Reply-To: <ca5558b48566d2b5eefa4c067966c284c30f415f.camel@linuxfoundation.org>
On 8/7/18 9:56 AM, Richard Purdie wrote:
> On Tue, 2018-08-07 at 11:44 +0100, richard.purdie@linuxfoundation.org
> wrote:
>> On Tue, 2018-08-07 at 17:37 +0800, Kang Kai wrote:
>>> On 2018年08月06日 22:51, Mark Hatle wrote:
>>>>>
>>>>>> resolvconf -> bash
>>>>>> weston-init -> weston kbd
>>>>>
>>>>> weston RRECOMMENDS weston-init?
>>>
>>> weston-init install init file which calls weston or weston-launch
>>> from
>>> package weston and openvt from package kbd.
>>
>> Agreed.
>>
>> My worry is that this move effectively makes allarch usesless since
>> any
>> script using an interpreter will now need to be not allarch since
>> most
>> interpreters are not allarch.
>>
>> I'm not sure this is a good move...
>
> Thinking about this further, we could just disable allarch if multilib
> is enabled? That would seem to address most of the issues, not entirely
> satisfactorily but enough to make things work... ?
Yes, this would resolve some of the concerns. We already know that these
allarch SHOULD be identical for all multilibs, so install space should not be an
issue, it's only build time concerns.
--Mark
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2018-08-07 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 1:49 [PATCH V2 0/2] Remove allarch from recipes which rdeps TUNE_PKGARCH packages kai.kang
2018-08-03 1:49 ` [PATCH 1/2] remove allarch from recipes which rdepends on " kai.kang
2018-08-03 21:28 ` richard.purdie
2018-08-06 14:51 ` Mark Hatle
2018-08-07 9:37 ` Kang Kai
2018-08-07 10:44 ` richard.purdie
2018-08-07 14:56 ` Richard Purdie
2018-08-07 17:07 ` Mark Hatle [this message]
2018-08-03 1:49 ` [PATCH 2/2] layer.conf: update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS kai.kang
2018-08-03 2:32 ` ✗ patchtest: failure for Remove allarch from recipes which rdeps TUNE_PKGARCH packages (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-08-03 0:53 [PATCH 0/2] Remove allarch from recipes which rdeps TUNE_PKGARCH packages kai.kang
2018-08-03 0:53 ` [PATCH 1/2] remove allarch from recipes which rdepends on " 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=eaca6350-e83c-129a-20fa-1484dab18cf5@windriver.com \
--to=mark.hatle@windriver.com \
--cc=Kai.Kang@windriver.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