[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Version of package fontforge
From: |
Ricardo Wurmus |
Subject: |
Re: Version of package fontforge |
Date: |
Wed, 05 Jun 2019 12:07:09 +0200 |
User-agent: |
mu4e 1.2.0; emacs 26.2 |
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