Hi Ben,
On Sun, Apr 16, 2017 at 10:42:42PM +0800, Ben Coman wrote:
> On Sat, Apr 15, 2017 at 4:34 PM, Luke Gorrie <l...@snabb.co> wrote:
> > On 15 April 2017 at 10:08, Alistair Grant <akgrant0...@gmail.com>
> > wrote:
> >
> > Grabbing the source directly from Git is attractive if (a) I know
> > that I am choosing a good version and (b) I am able to build it in a
> > good way.
> >
> > Seems like a workable solution to (a) is to periodically check for a
> > new binary release, work out which commit it is based off, and build
> > that. This seems fairly reasonable and is probably also possible to
> > automate. (I suppose you got the commit-id from --version or from
> > checking Jenkins.)
> >
> > I see (b) as problematic though. The source tarball releases have a
> > simple build procedure ("make") while the Git checkouts require a
> > more involved one (bootstrapping the VM from an existing Pharo
> > image.)
>
> A historical perspective...
>
> Prior to this coming Release 6, Pharo had diverged from the parent
> build system used by OpenSmalltalk (nee Squeak-VM) such that (IIUC) it
> was driven from the Image generating the generated-C-sources plus the
> Cmake configuration. I guess this is what you describe as
> "bootstrap".
>
> However for Release 6 onwards, Pharo has returned to the fold and is
> directly using the OpenSmalltalk build system. The OpenSmalltalk build
> system does not require a build to invoke a Smalltalk image, and I
> notice elsewhere you've seen the ./ mvm script. Eliot currently
> manually updates the checked-in generated-C-sources at times he
> considers them stably generated from VMMaker-Image, although I think I
> saw recently some mention of doing CI on each VMMaker check-in..
Do you know how the linux zero conf scripts are / will be built?
My assumption has been that they are part of the image build.
Thanks,
Alistair
