Re: [isabelle-dev] NEWS: Isabelle DejaVu fonts

2018-11-30 Thread Makarius
On 24/11/2018 19:51, Makarius wrote: > > *** Isabelle/jEdit Prover IDE *** > > * Fonts for the text area, gutter, GUI elements etc. use the "Isabelle > DejaVu" collection by default, which provides uniform rendering quality > with the usual Isabelle symbols. For Java/Swing GUI elements this >

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Jonathon Fernyhough
On 30/11/2018 14:55, Makarius wrote: > On 30/11/2018 14:15, Jonathon Fernyhough wrote: >> >> I'm currently packaging Isabelle2018 (in deb format) for deployment to >> several machines. These packages should contain some default heaps so >> users can get on with what they're doing and avoid

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Makarius
On 30/11/2018 18:56, Jonathon Fernyhough wrote: >> >>> However, a Debian packaging file is the correct approach for local >>> deployment to multiple Debian/Ubuntu machines. >> >> It is one approach, but typically causes problems. > > Given the size of the Debian repositories and the range of

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Jonathon Fernyhough
On 30/11/2018 16:36, Makarius wrote: > On 30/11/2018 16:30, Jonathon Fernyhough wrote: >> On 30/11/2018 14:55, Makarius wrote: >>> On 30/11/2018 14:15, Jonathon Fernyhough wrote: I'm currently packaging Isabelle2018 (in deb format) for deployment to several machines. These packages

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Thomas Sewell
I'd just like to confirm that other users have seen this issue. Colleagues of mine have tried to pre-build heaps on a build server and share them with other users. It could have saved CPU-hours, and in some cases, hours of humans waiting around, but it never worked. My understanding is that

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Makarius
On 30/11/2018 16:30, Jonathon Fernyhough wrote: > On 30/11/2018 14:55, Makarius wrote: >> On 30/11/2018 14:15, Jonathon Fernyhough wrote: >>> >>> I'm currently packaging Isabelle2018 (in deb format) for deployment to >>> several machines. These packages should contain some default heaps so >>>

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Makarius
On 30/11/2018 21:56, Makarius wrote: > On 30/11/2018 19:45, Thomas Sewell wrote: > > I am also unsure why "archive formats" got on this thread. The heap is a > binary build artifact, with its own internal structure. Its precise > content is somewhat non-deterministic, even when everything runs in

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Makarius
On 30/11/2018 19:45, Thomas Sewell wrote: > I'd just like to confirm that other users have seen this issue. > Colleagues of mine > > have tried to pre-build heaps on a build server and share them with other > users. It could have saved CPU-hours, and in some cases, hours of humans > waiting

[isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Jonathon Fernyhough
Hi! I'm currently packaging Isabelle2018 (in deb format) for deployment to several machines. These packages should contain some default heaps so users can get on with what they're doing and avoid duplicating hundreds of megabytes of data across user profiles. I'm trying to automate the heap

Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

2018-11-30 Thread Makarius
On 30/11/2018 14:15, Jonathon Fernyhough wrote: > > I'm currently packaging Isabelle2018 (in deb format) for deployment to > several machines. These packages should contain some default heaps so > users can get on with what they're doing and avoid duplicating hundreds > of megabytes of data