Davidisflash (Talk | contribs) (Installing openssh in MeeGo benefits developers using the SDK!) |
(categorise, wikify section headings and list) |
||
| (2 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | + | By David Medawar | |
| - | + | <b>Note: this tutorial may be extended to configurations not mentioned below, such as different hardware, etc.</b><br> | |
| + | <b>Note: all of the tutorial steps below were needed. Some unverified configurations may require more or less steps.</b> | ||
| - | + | ==Why openssh?== | |
| - | + | 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. | |
| - | + | ||
| - | 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, MeeGo SDK can | + | |
This document was verified using the following configuration: | This document was verified using the following configuration: | ||
| + | * VMPlayer latest version as of this document date | ||
| + | * Windows 7 64 bit development desktop | ||
| + | * Meego netbook 1.1 ia32 image (from Oct 2010, official) | ||
| + | ** Note: There have been known issues virtualizing MeeGo with some of the other MeeGo versions such as 1.1 Tablet and 1.1 UX | ||
| - | + | ==Steps== | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | Here are the steps that were needed to install openssh for MeeGo. | |
| + | <ol> | ||
| + | <li>Become root in the MeeGo terminal:<pre>$ sudo su</pre></li> | ||
| + | <li>If behind a firewall, ensure your proxy settings are correct:<pre># export http_proxy=http://<Proxy_address>:<Port_number></pre></li> | ||
| + | <li>Add the MeeGo SDK repository with the following command:<pre># zypper addrepo –f http://repo.meego.com/MeeGo/sdk/host/repos/meego/1.1/meego-sdk.repo</pre></li> | ||
| + | <li>Ensure all of your repo packages are up to date:<pre># zypper update</pre>(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)</li> | ||
| + | <li>Try:<pre>zypper install –t patch 1.1-Core-Updates</pre>This 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.</li> | ||
| + | <li>After reboot, enter terminal again, become root, and set proxy again, if necessary</li> | ||
| + | <li> | ||
| + | Edit the file <code>/etc/zypp/repos.d/core.repo</code> and set the following values: | ||
| + | <pre> | ||
| + | Enabled: 1 | ||
| + | Type: rpm-md | ||
| + | </pre> | ||
| + | </li> | ||
| + | <li>Make sure the repos are up to date:<pre># zypper ref</pre>You may get an error on one of the debug repos. This is OK.</li> | ||
| + | <li>Now install open ssh:<pre># zypper install openssh-server</pre>ssh is now ready to be used</li> | ||
| + | </ol> | ||
| - | + | [[Category:SDK]] | |
| + | [[Category:Tutorial]] | ||
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.repo and 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