From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martyn Welch <martyn.welch@collabora.co.uk>,
yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 1/2] package.bbclass: add prohibited-path qa test
Date: Tue, 14 Nov 2017 14:54:09 +0200 [thread overview]
Message-ID: <8291e8fe-44b3-6ec3-b0c7-f0075dde9317@linux.intel.com> (raw)
In-Reply-To: <ac750826-9931-85d1-35b4-106d774ee829@linux.intel.com>
On 11/14/2017 02:47 PM, Alexander Kanavin wrote:
> I think this situation is an image configuration problem, not a package
> qa problem. If a package wants to install something in a location that
> is deemed inappropriate by the local config, there's a reason behind it,
> the fix may not be easy to develop, and will likely be useless or even
> unacceptable to other users of the recipe. It's better to reconfigure
> the mount points.
Oh and another point I forgot: some files are created at do_rootfs time
when packages are installed onto the image, so they won't be caught by
this check at all. Better to do it at the last moment.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martyn Welch <martyn.welch@collabora.co.uk>,
yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] package.bbclass: add prohibited-path qa test
Date: Tue, 14 Nov 2017 14:54:09 +0200 [thread overview]
Message-ID: <8291e8fe-44b3-6ec3-b0c7-f0075dde9317@linux.intel.com> (raw)
In-Reply-To: <ac750826-9931-85d1-35b4-106d774ee829@linux.intel.com>
On 11/14/2017 02:47 PM, Alexander Kanavin wrote:
> I think this situation is an image configuration problem, not a package
> qa problem. If a package wants to install something in a location that
> is deemed inappropriate by the local config, there's a reason behind it,
> the fix may not be easy to develop, and will likely be useless or even
> unacceptable to other users of the recipe. It's better to reconfigure
> the mount points.
Oh and another point I forgot: some files are created at do_rootfs time
when packages are installed onto the image, so they won't be caught by
this check at all. Better to do it at the last moment.
Alex
next prev parent reply other threads:[~2017-11-14 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 19:19 [PATCH v2 1/2] package.bbclass: add prohibited-path qa test Martyn Welch
2017-11-13 19:19 ` [PATCH v2 2/2] ref-manual: Add documentation for prohibited-path QA test Martyn Welch
2017-11-13 19:39 ` ✗ patchtest: failure for "[v2] package.bbclass: add proh..." and 1 more Patchwork
2017-11-14 12:47 ` [OE-core] [PATCH v2 1/2] package.bbclass: add prohibited-path qa test Alexander Kanavin
2017-11-14 12:47 ` Alexander Kanavin
2017-11-14 12:54 ` Alexander Kanavin [this message]
2017-11-14 12:54 ` Alexander Kanavin
2017-11-14 13:01 ` [OE-core] " Andreas Oberritter
2017-11-14 13:01 ` Andreas Oberritter
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=8291e8fe-44b3-6ec3-b0c7-f0075dde9317@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martyn.welch@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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 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.