From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Why are the __DATE__ and __TIME__ fixed in the OSELAS Toolchain or PTXDist ?
Date: Wed, 21 Jul 2021 19:35:04 +0200 [thread overview]
Message-ID: <20210721173503.674owtnqc5p4o4iy@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <693eb2be-a75a-2f9e-5ede-cdd86add851d@ppc-ag.de>
[-- Attachment #1.1: Type: text/plain, Size: 1995 bytes --]
Hello Mircea,
On Wed, Jul 21, 2021 at 04:08:30PM +0200, Mircea Ciocan wrote:
>
> On 21.07.21 15:36, Alexander Dahl wrote:
> > The reason is so called reproducible builds:
> >
> > https://reproducible-builds.org/
> >
> > You can change behaviour in your BSP through the
> > REPRODUCIBLE_TIMESTAMP_* variables. Access it from the menu through
> > "Project Name & Version" ---> "SOURCE_DATE_EPOCH timestamps source"
> >
> > Greets
> > Alex
> >
> Thanks a lot Alex,
>
> I was starting to tear what little hair I have left, of course it had to be
> some google sponsored useless garbage :-(, oh well, at least is disable-able
> ;-).
Maybe you judged only after a quick glance? I would not call it
useless. See https://wiki.debian.org/ReproducibleBuilds/About on
motivation for it for example. As a user concerned about integrity of
the software I'm running, this approach is desirable.
As a developer eventually shipping firmware built by a ptxdist based
BSP, I'm also interested in reproducible build artefacts.
You might not need it for your usecases, other people would disagree,
thus calling it garbage … well … I would not do that.
> Best way is to run:
>
> ./ptxdist setup -> "Developer Options" -> "disable reproducible builds"
>
> and get rid of it, the following gem is from the "feature" help, I think it
> describes it nicely why is junk:
>
> "This can be confusing during development. E.g. The Linux kernel build
> timestamp never changes and cannot be used to ensure that the correct kernel
> image is used. Enable this option to get a new timestamp for every PTXdist
> call."
Junk, garbage, see above.
With kind greetings
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-07-21 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 13:02 Mircea Ciocan
2021-07-21 13:36 ` Alexander Dahl
2021-07-21 14:08 ` Mircea Ciocan
2021-07-21 17:35 ` Alexander Dahl [this message]
2021-07-21 15:35 ` Christian Melki
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=20210721173503.674owtnqc5p4o4iy@falbala.internal.home.lespocky.de \
--to=post@lespocky.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