opsi Version 3.3.1 - opsi Download - uib
opsi Version 3.3.1 - opsi Download - uib
opsi Version 3.3.1 - opsi Download - uib
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4. Localboot products: automatic software distribution with <strong>opsi</strong><br />
we create the folders 'CLIENT_DATA.CompanyX' and 'CLIENT_DATA.CustomerY'.<br />
In both the new directories you create another folder 'custom_ins_dir' which<br />
contains the additional software of the respective version. Later on, when installing the<br />
package on a server, the custom folder 'custom_ins_dir' will become a direct<br />
subdirectory of the main product folder:<br />
/home/<strong>opsi</strong>product/softprod/custom_ins_dir<br />
It is also possible to create another wInst-script in this directory, which can be called<br />
from the actual setup wInst-script during client installation. The custom wInst-script can<br />
be started from the main wInst-script like this:<br />
if FileExists("%ScriptPath%\custom_ins_dir\custom.ins")<br />
sub "%ScriptPath%\custom_ins_dir\custom.ins"<br />
endif<br />
To pack the product package you will have to change to the base product directory<br />
'/home/<strong>opsi</strong>product/softprod/'. Then pack the product for 'CompanyX' by calling<br />
'makeproductfile -i CompanyX'. Use the same name as the corresponding<br />
CLIENT_DATA-directory !<br />
So: CLIENT_DATA. => makeproductfile -i .<br />
The request for packing the package for 'CustomerY' is done similar:<br />
'makeproductfile -i CustomerY'<br />
The base version of the package (without any custom extension) will be packed by just<br />
calling 'makeproductfile' without -i parameter.<br />
The custom package<br />
softprod.-_.<strong>opsi</strong><br />
can be distributed and installed like any other packet.<br />
74