From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3 1/3] config/setup: make reproducible builds configurable
Date: Fri, 8 Feb 2019 14:48:07 +0100 [thread overview]
Message-ID: <20190208134807.77zhrn3gd332gkw6@pengutronix.de> (raw)
In-Reply-To: <20181221100640.8126-1-florian.baeuerle@allegion.com>
On Fri, Dec 21, 2018 at 10:06:59AM +0000, Baeuerle, Florian wrote:
> Some of ptxdist's packages use SOURCE_DATE_EPOCH to make the build
> results predictable. Make this behaviour more configurable via a newly
> introduced ptxdist setup options.
>
> By default, this will set SOURCE_DATE_EPOCH to the year and month of the
> used OSELAS Toolchain version. If the used toolchain is not an
> OSELAS-Toolchain, the PTXdist version is used as a fallback.
>
> Signed-off-by: Florian Bäuerle <florian.baeuerle@allegion.com>
Sorry for the late reply. This got lost on my side.
> ---
> config/setup/Kconfig | 47 ++++++++++++++++++++++++++
> config/setup/ptxdistrc.default | 5 +++
> scripts/lib/ptxd_lib_reproducible.sh | 49 +++++++++++++++++++++++++++-
> 3 files changed, 100 insertions(+), 1 deletion(-)
>
> diff --git a/config/setup/Kconfig b/config/setup/Kconfig
> index 990da03a1..10adb970d 100644
> --- a/config/setup/Kconfig
> +++ b/config/setup/Kconfig
> @@ -264,6 +264,53 @@ config SETUP_DISABLE_LOCAL_CHECK
> may fail under certain circumstances.
> Disable this check at your own risk.
>
> +config SETUP_DISABLE_REPRODUCIBLE
> + bool
> + prompt "disable reproducible builds"
> + help
> + By default ptxdist will build some packages in a
> + reproducible way by injecting fake timestamps, user and
> + host name into the build.
> +
The switch to disable this should be in setup ...
> +if !SETUP_DISABLE_REPRODUCIBLE
> +
> +choice
> + prompt "Fake timestamps source"
> + default SETUP_REPRODUCIBLE_TIMESTAMP_TOOLCHAIN
> +
> + config SETUP_REPRODUCIBLE_TIMESTAMP_TOOLCHAIN
> + bool
> + prompt "toolchain version"
> +
> + config SETUP_REPRODUCIBLE_TIMESTAMP_PTXDIST
> + bool
> + prompt "ptxdist version"
> +
> + config SETUP_REPRODUCIBLE_TIMESTAMP_CUSTOM
> + bool
> + prompt "custom timestamp"
> +
> +endchoice
... but the choice should be part of the pxconfig. I would accept a option
to disable this here too, but I don't think that's necessary.
In my opinion disabling reproducible builds is strictly a development
feature.
> +
> +config SETUP_REPRODUCIBLE_TIMESTAMP
> + string
> + default "toolchain" if SETUP_REPRODUCIBLE_TIMESTAMP_TOOLCHAIN
> + default "ptxdist" if SETUP_REPRODUCIBLE_TIMESTAMP_PTXDIST
> + default "custom" if SETUP_REPRODUCIBLE_TIMESTAMP_CUSTOM
> +
> +if SETUP_REPRODUCIBLE_TIMESTAMP_CUSTOM
> +
> +config SETUP_REPRODUCIBLE_TIMESTAMP_STRING
> + string
> + prompt "Fake timestamp"
> + default "2018-11-01 UTC"
I don't think we should provide a default. This should be an explicit
choice. But maybe put this as an example in the help text.
> + help
> + Supply a custom fake timestamp to be injected to the build.
> + The timestamp is passed to 'date --date'.
> +
> +endif
> +endif
> +
> config SETUP_ENV_WHITELIST
> string "environment variable whitelist (space separated)"
> help
> diff --git a/config/setup/ptxdistrc.default b/config/setup/ptxdistrc.default
> index 397b78eb7..8aa7dcc9a 100644
> --- a/config/setup/ptxdistrc.default
> +++ b/config/setup/ptxdistrc.default
> @@ -61,6 +61,11 @@ PTXCONF_SETUP_JAVA_SDK="/usr/lib/jvm/default-java"
> # Developer Options
> #
> # PTXCONF_SETUP_DISABLE_LOCAL_CHECK is not set
> +# PTXCONF_SETUP_DISABLE_REPRODUCIBLE is not set
> +PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP_TOOLCHAIN=y
> +# PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP_PTXDIST is not set
> +# PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP_CUSTOM is not set
> +PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP="toolchain"
> PTXCONF_SETUP_ENV_WHITELIST=""
> # PTXCONF_SETUP_COMMON_CACHE is not set
> # PTXCONF_SETUP_GEN_DEP_TREE is not set
> diff --git a/scripts/lib/ptxd_lib_reproducible.sh b/scripts/lib/ptxd_lib_reproducible.sh
> index e2e664ba8..98c528ac2 100644
> --- a/scripts/lib/ptxd_lib_reproducible.sh
> +++ b/scripts/lib/ptxd_lib_reproducible.sh
> @@ -8,8 +8,55 @@
> # see the README file.
> #
>
> +ptxd_timestamp_ptxdist() {
> + ptxd_reply="${PTXDIST_VERSION_YEAR}-${PTXDIST_VERSION_MONTH}-01 UTC"
> +}
> +
> +ptxd_timestamp_toolchain() {
> + local oselas_ptxconfig="$(readlink -f "${PTXDIST_TOOLCHAIN}/ptxconfig")"
> +
> + if [ -e "${oselas_ptxconfig}" ]; then
> + local oselas_version="$(source "${oselas_ptxconfig}" && echo ${PTXCONF_CONFIGFILE_VERSION})"
local oselas_version="$(ptxd_get_kconfig "${oselas_ptxconfig}" PTXCONF_CONFIGFILE_VERSION)"
> + local orig_IFS="${IFS}"
> + local IFS="."
> + set -- ${oselas_version}
> + IFS="${orig_IFS}"
> + ptxd_reply="${1}-${2}-01 UTC"
> + else
> + echo "${PTXDIST_LOG_PROMPT}warning: cannot deduce timestamp from toolchain, falling back to PTXdist version for reproducible timestamp"
> + ptxd_timestamp_ptxdist
No. Just fail here. With the options in the ptxconfig that should be ok.
> + fi
> +}
> +
> +ptxd_timestamp_custom() {
> + local ts="${PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP_STRING}"
With the change I requested above, you'll need to use ptxd_get_ptxconf
here (and for the other PTXCONF_* variables from ptxconfig.
> +
> + if ! date --date "${ts}" > /dev/null 2>&1; then
> + echo "${PTXDIST_LOG_PROMPT}warning: '${ts}' is not a valid timestamp, falling back to toolchain for reproducible timestamp"
> + ptxd_timestamp_toolchain
> + else
> + ptxd_reply="${ts}"
> + fi
> +}
> +
> ptxd_lib_reproducible() {
> - SOURCE_DATE_EPOCH="$(echo $(date --date="${PTXDIST_VERSION_YEAR}-${PTXDIST_VERSION_MONTH}-01 UTC" "+%s"))"
> + if [ "${PTXCONF_SETUP_DISABLE_REPRODUCIBLE}" = "y" ]; then
> + ptxd_timestamp_ptxdist
I don't think that this is correct. Maybe:
ptxd_reply="$(date "+@%s")"
> + else
ptxd_timestamp_$(ptxd_get_ptxconf PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP)
should work as expected.
Michael
> + case "${PTXCONF_SETUP_REPRODUCIBLE_TIMESTAMP}" in
> + "custom")
> + ptxd_timestamp_custom
> + ;;
> + "ptxdist")
> + ptxd_timestamp_ptxdist
> + ;;
> + *)
> + ptxd_timestamp_toolchain
> + ;;
> + esac
> + fi
> +
> + SOURCE_DATE_EPOCH="$(echo $(date --date="${ptxd_reply}" "+%s"))"
> export SOURCE_DATE_EPOCH
>
> PTXDIST_BUILD_TIMESTAMP="$(echo $(date --utc --date @${SOURCE_DATE_EPOCH} +%Y-%m-%dT%H:%M+0000))"
> --
> 2.19.2
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-02-08 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 14:52 [ptxdist] [PATCH v2 1/4] " Baeuerle, Florian
2018-12-12 14:52 ` [ptxdist] [PATCH v2 2/4] barebox: depend on HOST_LZOP Baeuerle, Florian
2018-12-13 11:16 ` Michael Olbrich
2018-12-13 13:02 ` Baeuerle, Florian
2018-12-13 13:34 ` Michael Olbrich
2018-12-14 11:54 ` Baeuerle, Florian
2018-12-12 14:52 ` [ptxdist] [PATCH v2 3/4] barebox: add support for reproducible build Baeuerle, Florian
2018-12-12 14:52 ` [ptxdist] [PATCH v2 4/4] barebox_mlo: " Baeuerle, Florian
2018-12-21 10:06 ` [ptxdist] [PATCH v3 1/3] config/setup: make reproducible builds configurable Baeuerle, Florian
2018-12-21 10:07 ` [ptxdist] [PATCH v3 2/3] barebox: add support for reproducible build Baeuerle, Florian
2018-12-21 10:07 ` [ptxdist] [PATCH v3 3/3] barebox_mlo: " Baeuerle, Florian
2019-02-08 9:33 ` [ptxdist] [PATCH v3 1/3] config/setup: make reproducible builds configurable Baeuerle, Florian
2019-02-08 13:48 ` Michael Olbrich [this message]
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=20190208134807.77zhrn3gd332gkw6@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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