update from SuperBuild

[paskino]

closes #200

[KrisThielemans]

I really don't know if this does the trick. I cannot imagine, as it's still going to do the UPDATE.sh that you've just modified.

Also, an update will definitely fail without the -s switch.

I don't have the bandwidth to test this I'm afraid, which is why I thought we'd agree to just write a message with a recommendation. But if you can test it, and it works, I'm happy!

[paskino]

I tested this as in SyneRBI/SIRF-SuperBuild#747

[KrisThielemans]

I strongly suggest to port some of this to the SIRf-SuperBuild repo, and in this repo just let UPDATE.sh error out with a message that tells users what to do. (i.e. update their local version of the SB, and execute its UPDATE.sh -s. Otherwise we will have to keep this repo up-to-date for the next one anyway.

However, in the SB, I'd rather keep the original INSTALL* files, and let those call the docker files. Reasons:

• I feel this allows us to do VirtualBox specific stuff.
• the INSTALL scripts are used in https://github.com/SyneRBI/SIRF-SuperBuild/blob/master/cloud/terraform/azure/packer/scripts/provision.sh
• they have logical names in my opinion :-)

[paskino]

Especially the file names in the docker directory aren't very clear!

[KrisThielemans]

Closing here as we won't keep the repo up-to-date. Ideas here are in
SyneRBI/SIRF-SuperBuild#755 and SyneRBI/SIRF-SuperBuild#758