all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ison <ison@airmail.cc>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Version of package fontforge
Date: Wed, 5 Jun 2019 23:51:18 -0600	[thread overview]
Message-ID: <20190606055117.afhzldbn4s6lwdym@cf0> (raw)
In-Reply-To: <87k1e0cpma.fsf@elephly.net>

Assuming it would be ok to just set the date to the package version date, which
sounds reproducible to me, then using the date produced by:
date -u -d "20190317" +'%s'
gives: 1552780800

I did a quick test to set the configure-flags with this value:

  (arguments
    (append (package-arguments fontforge)
            '(#:configure-flags (list "SOURCE_DATE_EPOCH=1552780800"))))

And with that, if I run fontforge --version I get:

  Copyright (c) 2000-2018 by George Williams. See AUTHORS for Contributors.
   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
   with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
   Based on sources from 00:00 UTC 17-Mar-2019-ML-D.
   Based on source from git with hash: 
  fontforge 00:00 UTC 17-Mar-2019
  libfontforge 20190317

Which looks like the desired output.
However, the best solution would probably be to programmatically obtain
1552780800. I'm not sure what the best way would be to do that. I'm looking at
some of the available date commands inside SRFI-19 and I don't see anything for
converting a string like "20190317" to seconds.

  reply	other threads:[~2019-06-06  5:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 10:41 Version of package fontforge Tilman List
2019-06-05 10:07 ` Ricardo Wurmus
2019-06-06  5:51   ` ison [this message]
2019-06-07  4:53 ` ison
2019-06-11 10:20   ` Ludovic Courtès
2019-06-28 21:06   ` Tilman List

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=20190606055117.afhzldbn4s6lwdym@cf0 \
    --to=ison@airmail.cc \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.