By David Medawar
Note: this tutorial may be extended to configurations not mentioned below, such as different hardware, etc.
Note: all of the tutorial steps below were needed. Some unverified configurations may require more or less steps.
There is overhead in manually copying over, installing, and running an RPM on a MeeGo target device every time source code is rebuilt. SSH, in conjunction with a virtualized MeeGo software stack on the same development system, streamlines the process of testing significantly with the click of the "Run" option in MeeGo SDK.
Here, these steps assume that the developer has setup a virtualized MeeGo software stack for quick app testing. This especially helps in the case where an actual MeeGo target isn't readily available for use. After building source code, the MeeGo SDK can connect to the virtualized MeeGo stack through the guest on the same system over ssh. This allows for immediately running a new build without delay.
This document was verified using the following configuration:
Here are the steps that were needed to install openssh for MeeGo.
$ sudo su
# export http_proxy=http://<Proxy_address>:<Port_number>
# zypper addrepo –f http://repo.meego.com/MeeGo/sdk/host/repos/meego/1.1/meego-sdk.repo
# zypper update(I got a bunch of errors and this step may not be necessary for the solution that we arrive at, but for the sake of reproducibility, give it a try)
zypper install –t patch 1.1-Core-UpdatesThis is recommended here: https://bugs.meego.com/show_bug.cgi?id=10113. I chose "solution 1" when asked to uninstall previous packages. Reboot the virtual machine when prompted to do so.
/etc/zypp/repos.d/core.repoand set the following values:
Enabled: 1 Type: rpm-md
# zypper refYou may get an error on one of the debug repos. This is OK.
# zypper install openssh-serverssh is now ready to be used