On Sat, 1 Dec 2018 at 02:19, Alexandre Garreau <galex-...@galex-713.eu> wrote:
> Hi, > > I tried to compile itself because I’m usually uncomfortable with using > binaries downloaded from the internet whose sources couldn’t be checked > afterwards. I don’t know the status of Pharo regarding Deterministic > Builds, but I have come anyway to become more comfortable in trusting > what comes from the distro I use and only that… > > But I saw the bootstrap process involve redownloading a binary image > anyway… I’d have just prefered to recompile it to be sure, as I’m > usually more comfortable with this idea. Normally compiling a new > language is —though long— not that difficult. > Traditional Smalltalk systems don't do a bootstrap. Indeed its conceivable(?) that there exist some objects floating around in Images distributed by vendors today that were created in the 1980s. In spite of the advantages of the Image concept saving the whole system state, it does impact reproducability, and is one of the common criticisms of Smalltalk. Pharo has put a lot of effort into producing a bootstrap system run by CI every commit, but there may still be some rough edges when used outside the CI. You sound like you may have already looked into these, but anyway you may get some hints from... * https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/1427/consoleFull * https://github.com/pharo-project/pharo/blob/development/Jenkinsfile cheers -ben
