From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Max Krummenacher <max.oss.09@gmail.com>
Cc: Max Krummenacher <max.krummenacher@toradex.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] libsolv: don't pick up bundled db from host rpm
Date: Tue, 30 May 2017 00:11:49 +0100 [thread overview]
Message-ID: <1496099509.25229.144.camel@linuxfoundation.org> (raw)
In-Reply-To: <e9b75721-f3e3-7f3f-e781-58df67b4130a@linux.intel.com>
On Mon, 2017-05-29 at 18:54 +0300, Alexander Kanavin wrote:
> I see. You are right here. I admit I don't fully understand if it's
> generally okay for -native recipes to look around in (and later use)
> host include directories like that, as we're striving towards
> reproducible builds, and this behavior is not supportive of them.
> Richard, can we have your say please?
Its unavoidable really, we have to have some host system we build on as
we need a compiler/headers from it. Even if you build a gcc-native,
what would you compile it with? :)
If you do want to avoid the risk, you'd choose your own custom base OS
(or container) and then always build on that. It would then be both
reproducible and deterministic. We don't want to mandate a specific
host configuration out the box though.
So this patch avoids an issue. We don't tend to run into too many
issues like this one thankfully.
Cheers,
Richard
next prev parent reply other threads:[~2017-05-29 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 20:35 [PATCH v2] libsolv: don't pick up bundled db from host rpm Max Krummenacher
2017-05-29 10:50 ` Alexander Kanavin
2017-05-29 13:00 ` Max Krummenacher
2017-05-29 13:06 ` Max Krummenacher
2017-05-29 15:54 ` Alexander Kanavin
2017-05-29 23:11 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-19 15:48 Max Krummenacher
2017-05-19 15:51 ` Burton, Ross
2017-05-19 16:08 ` Max Krummenacher
2017-05-22 13:08 ` Alexander Kanavin
2017-05-22 21:32 ` Max Krummenacher
2017-05-23 13:10 ` Alexander Kanavin
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=1496099509.25229.144.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=max.krummenacher@toradex.com \
--cc=max.oss.09@gmail.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