From mboxrd@z Thu Jan 1 00:00:00 1970 From: ison Subject: Re: Version of package fontforge Date: Wed, 5 Jun 2019 23:51:18 -0600 Message-ID: <20190606055117.afhzldbn4s6lwdym@cf0> References: <87k1e0cpma.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([209.51.188.92]:52170) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hYlJD-0000si-8F for help-guix@gnu.org; Thu, 06 Jun 2019 01:51:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hYlJA-0004Qa-Te for help-guix@gnu.org; Thu, 06 Jun 2019 01:51:30 -0400 Received: from [2a06:1700:0:b:1::1] (port=36448 helo=cock.li) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hYlJA-0004Gp-0u for help-guix@gnu.org; Thu, 06 Jun 2019 01:51:28 -0400 Content-Disposition: inline In-Reply-To: <87k1e0cpma.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: help-guix@gnu.org 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 with many parts BSD . 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.