Ok, best as I can tell, the GCL in the binaries is taken from GOOG_HOME on the machine on which the release is built. It is not actively pulled from Git, unless it's built on our build VM using 'jenkins.xml'.
Since the Installer uses the binaries, this means it never has to pull the GCL sources itself, so it doesn't matter that the Installer cannot run Git. EdB On Fri, Jun 27, 2014 at 12:16 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: > exec. But I don't think we need it for GCC/GCL. I think I'm all set >> until the GCL package on GH changes. >> > > You should be able to always dl this zip: > > https://github.com/google/closure-library/archive/master.zip > > That is the only one that counts, as it basically contains the same files > as the git clone does, namely the HEAD of the repo... There are no > 'versions' of the GCL on GitHub per se. > > EdB > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
