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

[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 the "hash the world" mechanism for capturing

the state of the dependencies sometimes captures the absolute names of files.

This breaks down in the obvious way if, for instance, we can't assume that all

the target users have the same username. None of this has anything to do

with the archive format.


These observations may all be out of date.

Cheers,
    Thomas.


________________________________
From: isabelle-dev <isabelle-dev-bounces at mail46.informatik.tu-muenchen.de> on behalf of Makarius <makarius at sketis.net>
Sent: Friday, November 30, 2018 7:13:36 PM
To: Jonathon Fernyhough; isabelle-dev at mail46.informatik.tu-muenchen.de
Subject: Re: [isabelle-dev] Support in `isabelle build` for SOURCE_DATE_EPOCH

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 software they
> make available I'm not really sure this is true.

Hopefully this is not another attempt at an official Debian package of
Isabelle. Many years ago, some people tried it, but it always caused
more problems than it solved. And today the system is more complex and
more easily destroyed by packaging it.

These days I see big and complex products doing it our way: providing a
fully integrated distribution for end-users that by-passes OS package
managers.


        Makarius

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman46.in.tum.de/pipermail/isabelle-dev/attachments/20181130/e69d22bd/attachment-0002.html>