1 person found this helpful
You can create a custom build using --setvars to create a different build for each flavor,
To download packages you can use the <httpGet> action in the <preBuildActionList>
But we recommend to automate the downloading of the build packages in advance in your own build system and use InstallBuilder to package them.
Thank you Michiel .. much appreciated. Sometimes you just need a little push in the right direction .
One other quick question -- if we are installing a Python 3 program is it recommended that we have the Python SetupTools and other pythonish things built to use within Install Builder's scripts?
So I use runTools to run
-make or gmake
Do these steps get included in the progress bar count?
I was contemplating using postinstaller.sh to run all these integrated installers but I would rather do it in the sequence within installbuilder's installer rather than in a shell script reflecting my original Dockerfile approach. So I have been slowly getting my head around installBuilder trying to figure out if it accommodates my relatively complex install process.
Here is the process:
First I install all the OS level dependencies in either SUSE, RH, Centos, or Ubuntu using the core packaging tools for that platform (i.e. zypper, yum, dnf, apt etc)
After the OS level dependencies I install
1) python pip update
4) all python libraries using pip
5) run a 3rd party library installer -- via an executible with a bunch of cli options
a) includes running make, setup.py build, setup.py install
6) install a database - sqlcipher (a sqllite add-on) includes running config, make
7) install another 3rd party library install -- setup.py build, setup.py install
8) setting environment variables