Once a package has been built, it must be deployed to the device (or SDK target, in the case of -devel packages). Depending on whether the package was built locally or remotely, there are different ways to deploy the package to the device.
Deploying Local RPMs
For packages built locally, the developer will have .rpm files which they wish to deploy. To deploy these packages to the device, the developer can first use
scp to copy the .rpm from the host computer to the device via ssh. Then, the package can be installed by issuing the
rpm -Uvh --force <package.rpm> command from a devel-su prompt (e.g.,
devel-su rpm -Uvh --force <package.rpm>). In some cases, rebooting the device may be necessary to force any changes to take effect.
Note that packages installed in this fashion ("sideloaded") may cause conflicts with packages installed from repositories. Future upgrades will not necessarily succeed cleanly if a sideloaded .rpm with incorrect version information is installed.
Deploying From Repository
When the Open Build Service builds a package, that package becomes available in a repository (usually, the user's home project repository). The package may then either be downloaded directly as an .rpm and installed as described in the above section on deploying local .rpm files, or the repository can be added to the device or SDK target as a software update repository, and the device or SDK target can be updated to install the package from that newly added repository.
The OBS repository can be added to the device or SDK target rootfs repository via:
ssu ar <repo_name> <repo_url>
The available packages can then be installed to the device via
devel-su pkcon refresh
devel-su pkcon install <pkg_name>
or to the SDK via:
zypper ref -f
zypper in <pkg_name>
from an sdk-install-mode root prompt within ScratchBox2 (e.g.,
sb2 -t SailfishOS-armv7hl -m sdk-install -R).
You can use
ssu lr to list the available repositories.