Page Properties | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
Simply Simplify the process for upgrading an installation under Linux. This request was made by Nexway but will apply to all Linux customers.
Background and strategic fit
...
Proposed changes for Linux packages and installation script:
Currently there are two packages, sdk_linux.rpm (BRKTBOSsetup) and fw_linux.rpm (BRKTBOSsetup-fw). Combine them into a single package (sdk_linux.rpm) and just one package name (BRKTBOSsetup). (For reference, Solaris has a single package.) This also applies to the both the full package and the non-sr140 versionspackage.
After installation, the config directory contains btcall.cfg, callctrl.cfg, BT_CPARM.CFG, and other files. Identical copies of these three files will also be installed into the samples.cfg subdirectory. (There was discussion about using CM Synergy "links", but that is not applicable. This turns out to be an installation/packaging issue, only.) For consistency, this will/should also be done for Windows and Solaris.
Change the RPM removal scripts so that they will stop Bostsrv, uninstall the driver, and remove the /etc/startbost scriptdriver.
Modify the setup.sh installation script as follows:
...
There is currently a very small and unneeded difference between the setup.sh script for the packages that include the SR140 and those that do not. The files will be made identical.
If the version of the SDK currently installed is earlier than 6.7.3, then the install.sh script will do what the setup.sh does: stop Bostsrv, uninstall the driver, and remove the driver.
Requirements
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | ||||
...