All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: douglas.royds@taitradio.com
Cc: openembedded-core@lists.openembedded.org
Subject: Overriding SDE_FILE
Date: Mon, 24 Feb 2020 08:25:01 +0100	[thread overview]
Message-ID: <8b666dc3-e5a6-0417-82bd-2b15190d223f@gmail.com> (raw)

Hi Douglas,

You updated a comment in reproducible_build.bbclass, commit 
e7b891b76954c784f5a93bd0a1c91315673ce40d:

> -# Once the value of SOURCE_DATE_EPOCH is determined, it is stored in the recipe's ${SDE_FILE}.
> +# Once the value of SOURCE_DATE_EPOCH is determined, it is stored in the recipe's SDE_FILE.
> +# If none of these mechanisms are suitable, replace the do_deploy_source_date_epoch task
> +# with recipe-specific functionality to write the appropriate SOURCE_DATE_EPOCH into the SDE_FILE.
> +#

But I can't really get this to work. What did work for me was to replace 
"do_create_source_date_epoch_stamp()" in my recipe:

do_create_source_date_epoch_stamp() {
     mkdir -p ${SDE_DIR}
     date -d "1981-03-03" "+%s" > ${SDE_FILE}
}

What is the intended way to achieve the thing I'm trying to do here ?

Cheers,
Jacob


             reply	other threads:[~2020-02-24  7:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  7:25 Jacob Kroon [this message]
2020-02-25 15:53 ` Overriding SDE_FILE Jacob Kroon
2020-02-27  5:46   ` Douglas Royds
2020-02-27 15:01     ` Joshua Watt
2020-02-27 16:45       ` Joshua Watt
2020-02-27 21:22         ` Douglas Royds
2020-02-27 21:49           ` Joshua Watt
2020-02-27 22:29             ` Douglas Royds
2020-02-27 22:34               ` Joshua Watt
2020-02-27 22:35                 ` Douglas Royds
2020-02-28 13:39                   ` Jacob Kroon
2020-02-28 13:41                     ` Jacob Kroon
2020-02-28 14:18                       ` Joshua Watt
2020-02-28 14:32                         ` Jacob Kroon

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=8b666dc3-e5a6-0417-82bd-2b15190d223f@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=douglas.royds@taitradio.com \
    --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.