From: Ricardo Wurmus <rekado@elephly.net>
To: Tilman List <tilman.list@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Version of package fontforge
Date: Wed, 05 Jun 2019 12:07:09 +0200 [thread overview]
Message-ID: <87k1e0cpma.fsf@elephly.net> (raw)
In-Reply-To: <c0f3345fb1355e97b9989d9545e1fb7c1781176c.camel@posteo.de>
Hi Tilman,
> when I tried to compile lilypond, I had some problems with the package
> fontforge. In Guix it is listed as version 20190317, but when I do "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 1-Jan-1970-ML-D.
> Based on source from git with hash:
> fontforge 00:00 UTC 1-Jan-1970
> libfontforge 19700101
We may need to patch fontforge. The version is derived from the current
date at build time:
fontforge-20190317/configure.ac:FONTFORGE_VERSIONDATE="$(date -u $FONTFORGE_DATE_OPTS +'%Y%m%d')"
fontforge-20190317/configure:#define FONTFORGE_VERSIONDATE_RAW $FONTFORGE_VERSIONDATE
And that’s what’s used in fontforge-20190317/fontforge/start.c.
We don’t run “date” during the configuration; during builds
SOURCE_DATE_EPOCH is set:
fontforge-20190317/configure.ac:FONTFORGE_DATE_NOW=${SOURCE_DATE_EPOCH:-$(date +'%s')}
We may need to patch fontforge so that these values are properly defined.
--
Ricardo
next prev parent reply other threads:[~2019-06-05 13:53 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 [this message]
2019-06-06 5:51 ` ison
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1e0cpma.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=tilman.list@posteo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).