From: Joshua Lock <joshua.lock@collabora.co.uk>
To: Christopher Larson <clarson@kergoth.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] insane.bbclass: add host-user-contaminated test
Date: Wed, 26 Aug 2015 15:24:00 +0100 [thread overview]
Message-ID: <55DDCC00.8090909@collabora.co.uk> (raw)
In-Reply-To: <CABcZAN=zY7JoSk+btg7=GLxnqaX_ZXwvj1Nv5Dz10RnqGNPDGg@mail.gmail.com>
On 26/08/15 15:20, Christopher Larson wrote:
>
> On Wed, Aug 26, 2015 at 7:19 AM, Christopher Larson <clarson@kergoth.com
> <mailto:clarson@kergoth.com>> wrote:
>
> On Wed, Aug 26, 2015 at 4:01 AM, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
> On 26 August 2015 at 09:44, Joshua Lock
> <joshua.lock@collabora.co.uk
> <mailto:joshua.lock@collabora.co.uk>> wrote:
>
> I do all of my builds on a separate partition in a directory
> hierarchy which is owned by my user - if I'm understanding
> this correctly I'll get QA WARNINGS for all of my builds
> with this change?
>
>
> The paths are prefixed with ${D} so pretend the commit log says
> "in packages".
>
>
> Heh, indeed, it's a package QA test. do_install runs under pseudo,
> so any newly created files there, or files chown'd to root, will be
> fine. If, however, a recipe does a cp -a or so to install without
> doing a chown, you'll end up with files in your rootfs owned by the
> user that did the build -- not good.
Indeed. Thanks for taking the time to clarify.
>
> I can re-submit with that commit message clarification, if needed? I
> rather thought the fact that it was in insane.bbclass, not
> sanity.bbclass, carried the necessary implication.
Personally I don't feel that's necessary - I should review with more
care (and coffee).
Thanks for the offer though.
Regards,
Joshua
next prev parent reply other threads:[~2015-08-26 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 22:19 [PATCH 0/3] Add checks for "host user contamination" Christopher Larson
2015-08-24 22:19 ` [PATCH 1/3] insane.bbclass: handle tests which need fakeroot Christopher Larson
2015-08-24 22:19 ` [PATCH 2/3] insane.bbclass: add host-user-contaminated test Christopher Larson
2015-08-26 8:44 ` Joshua Lock
2015-08-26 11:01 ` Burton, Ross
2015-08-26 14:19 ` Christopher Larson
2015-08-26 14:20 ` Christopher Larson
2015-08-26 14:24 ` Joshua Lock [this message]
2015-08-24 22:19 ` [PATCH 3/3] image.bbclass: add rootfs_check_host_user_contaminated Christopher Larson
2015-09-01 7:50 ` [PATCH 0/3] Add checks for "host user contamination" Richard Purdie
2015-09-01 7:52 ` Richard Purdie
2015-09-01 15:05 ` Christopher Larson
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=55DDCC00.8090909@collabora.co.uk \
--to=joshua.lock@collabora.co.uk \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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