From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] Makefile: add tainting support
Date: Thu, 6 Sep 2018 00:01:05 +0200 [thread overview]
Message-ID: <20180906000105.021f9ccc@windsurf> (raw)
In-Reply-To: <CA+_SqVZcTc2m4A9NiumRtPAd3B7cyZ7Od0Xf_SfQ9dcUqgXTvg@mail.gmail.com>
Hello,
On Wed, 5 Sep 2018 23:45:47 +0200, Angelo Compagnucci wrote:
> > So: do we care about host packages for "tainting" ? If we do care, how
> > do we handle this ?
>
> I think we can demand the decision to when we will have a host package
> that needs tainting support.
>
> Moreover, I don't think the demand for host packages that needs
> tainting support will be high in the future.
Then we need to make that explicit:
ifeq ($$($(2)_TYPE),host)
ifneq ($$($(2)_TAINTS),)
$$(error "Host package $(1) has $(2)_TAINTS set: not supported)
endif
endif
of course, please check that this really works as expected.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-05 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 16:06 [Buildroot] [PATCH v3 0/3] Add tainting support to buildroot Angelo Compagnucci
2018-09-05 16:06 ` [Buildroot] [PATCH v3 1/3] Makefile: add tainting support Angelo Compagnucci
2018-09-05 19:37 ` Thomas Petazzoni
2018-09-05 21:45 ` Angelo Compagnucci
2018-09-05 22:01 ` Thomas Petazzoni [this message]
2018-09-05 22:22 ` Angelo Compagnucci
2018-09-05 16:06 ` [Buildroot] [PATCH v3 2/3] docs/manual: adding infos about tainting Angelo Compagnucci
2018-09-05 16:06 ` [Buildroot] [PATCH v3 3/3] package/nodejs: taint the build on external modules Angelo Compagnucci
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=20180906000105.021f9ccc@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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