From: Adrian Bunk <bunk@stusta.de>
To: "André Draszik" <git@andred.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] bitbake.conf: omit XZ threads and RAM from sstate signatures
Date: Mon, 24 Feb 2020 16:31:55 +0200 [thread overview]
Message-ID: <20200224143155.GD27036@localhost> (raw)
In-Reply-To: <6c0d874e887dc5a2355d236d77e8ec771ea729f9.camel@andred.net>
On Mon, Feb 24, 2020 at 02:21:57PM +0000, André Draszik wrote:
>...
> Once the artefact has been created, it doesn't matter anymore how it
> was created, as long as the high-level options aren't being changed (like
> an explicit compression level, checksum method, etc.)
>...
meta-poky/conf/distro/poky.conf:INHERIT += "reproducible_build"
> Cheers,
> Andre'
cu
Adrian
next prev parent reply other threads:[~2020-02-24 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 12:59 [PATCH v2] bitbake.conf: omit XZ threads and RAM from sstate signatures André Draszik
2020-02-24 13:40 ` Adrian Bunk
2020-02-24 14:21 ` André Draszik
2020-02-24 14:31 ` Adrian Bunk [this message]
2020-02-24 14:58 ` André Draszik
2020-02-24 15:10 ` Adrian Bunk
2020-02-25 11:16 ` reproducible builds involving xz (was: Re: [PATCH v2] bitbake.conf: omit XZ threads and RAM from sstate signatures) André Draszik
2020-02-25 11:23 ` Richard Purdie
2020-02-24 16:44 ` [PATCH v2] bitbake.conf: omit XZ threads and RAM from sstate signatures Richard Purdie
2020-02-24 17:12 ` Adrian Bunk
2020-02-24 17:14 ` André Draszik
2020-02-24 17:32 ` Richard Purdie
2020-02-24 22:00 ` Adrian Bunk
2020-02-25 9:16 ` André Draszik
2020-02-25 9:54 ` Adrian Bunk
2020-02-26 15:26 ` xz threads / memlimit behaviour (was: Re: [PATCH v2] bitbake.conf: omit XZ threads and RAM from sstate signatures) André Draszik
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=20200224143155.GD27036@localhost \
--to=bunk@stusta.de \
--cc=git@andred.net \
--cc=openembedded-core@lists.openembedded.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.