From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Tainting support
Date: Tue, 6 Mar 2018 09:48:03 +0100 [thread overview]
Message-ID: <1520326085-18337-1-git-send-email-angelo@amarulasolutions.com> (raw)
Packages that need to resolve dependencies internally
and use a package manager would harm the reproducibility
of a build, moreover they escape the legal infrastructure
not giving enough informations on licensing.
This patch adds a tainting mechanism in the form of a
variable FOO_TAINTS that can be used to signal that
a package harms the reproducibility under certain
conditions.
This variable is later used to check if the build is
tainted or not. The build then aborts with an error
when the build is marked tainted and BR2_REPRODUCIBLE is
enabled.
This opens the door to include per language dependency
managers in buildroot.
Angelo Compagnucci (2):
Makefile: add tainting support
package/nodejs: taint the build on external modules
Makefile | 14 +++++++++++++-
package/nodejs/nodejs.mk | 1 +
package/pkg-generic.mk | 9 +++++++++
3 files changed, 23 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2018-03-06 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 8:48 Angelo Compagnucci [this message]
2018-03-06 8:48 ` [Buildroot] [PATCH 1/2] Makefile: add tainting support Angelo Compagnucci
2018-04-28 16:53 ` Thomas Petazzoni
2018-05-03 21:34 ` Angelo Compagnucci
2018-05-04 18:59 ` Arnout Vandecappelle
2018-03-06 8:48 ` [Buildroot] [PATCH 2/2] 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=1520326085-18337-1-git-send-email-angelo@amarulasolutions.com \
--to=angelo@amarulasolutions.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