[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failing CI builds
From: |
Werner LEMBERG |
Subject: |
Re: failing CI builds |
Date: |
Mon, 29 Jun 2020 09:07:36 +0200 (CEST) |
>> I got the following answer:
>>
>> METAFONT supports SOURCE_DATE_EPOCH variable. Try
>>
>> export SOURCE_DATE_EPOCH=10000
>> export FORCE_SOURCE_DATE=1
>>
>> I think MetaPost does not support the variables.
>
> I already tried this yesterday and it worked well for getting the
> same timestamps (I just exported a constant value in my shell).
> However, I'm still seeing differences in the generated fonts and
> also in the .svg files (which are non-binary, so diff actually shows
> me what changes).
Well, while Metafont has SOURCE_DATE_EPOCH support, Metapost hasn't
(yet – this will change in a few days so that the next TeXLive version
will contain it).
Recent versions of FontForge should have support too, BTW.
Werner
- Re: failing CI builds, (continued)
Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27
- Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27
- Re: failing CI builds, Werner LEMBERG, 2020/06/27
- Re: failing CI builds, Han-Wen Nienhuys, 2020/06/27
- Re: failing CI builds, Werner LEMBERG, 2020/06/27
- Re: failing CI builds, Werner LEMBERG, 2020/06/28
- Re: failing CI builds, Jonas Hahnfeld, 2020/06/28
- Re: failing CI builds,
Werner LEMBERG <=
- Re: failing CI builds, Jonas Hahnfeld, 2020/06/29
- Re: failing CI builds, Werner LEMBERG, 2020/06/29
- Re: failing CI builds, Jonas Hahnfeld, 2020/06/29