sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Edits to the "Setting Up Runtime Package Management" section. 

Paul Eggleton sent me corrected procedure.  I implemented his
changes.

(From yocto-docs rev: 581778c52493b662f449bbbed36453f161501c18)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-09-26 14:16:36 -07:00 committed by Richard Purdie
parent ec84110a74
commit d8d5841188
1 changed files with 95 additions and 95 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -3628,10 +3628,6 @@
You have a web server, such as Apache 2,
installed and configured on the development host.
</para></listitem>
<listitem><para>
You have <filename>createrepo</filename> installed on
the development host.
</para></listitem>
<listitem><para>
You enable package management on the target by
listing "package-management" in the
@ -3641,6 +3637,9 @@
</itemizedlist>
</para>
<section id='runtime-package-management-deb-rpm'>
<title>Using DEB and RPM</title>
<para>
Following are the steps to set up the optional repository.
This example assumes you are using RPM and the Apache 2
@ -3683,24 +3682,18 @@
/etc/init.d/apache2 reload
</literallayout>
</para></listitem>
<listitem><para>
Run BitBake on <filename>package-index</filename>
on the host
<literallayout class='monospaced'>
bitbake package-index
</literallayout>
</para></listitem>
<listitem><para>
Change your working directory to
<filename>tmp/deploy/rpm</filename> in the
<link linkend='build-directory'>Build Directory</link>.
</para></listitem>
<listitem><para>
Create the repository data on the host using
this command:
<literallayout class='monospaced'>
createrepo .
</literallayout>
</para>
<para>
<note>
If you're updating, add
<filename>&dash;&dash;update</filename> to save some time.
</note>
</para></listitem>
<listitem><para>
If you are using Security-Enhanced Linux (SELinux),
you need to label the files as being accessible
@ -3711,11 +3704,20 @@
</literallayout>
</para></listitem>
<listitem><para>
On the target machine, add the repository to Smart.
For <filename>somealias</filename>, provide a local
alias for the repository:
On the target machine, add the repository to Smart
for every package architecture.
To see the list of package architectures, just list
the contents of the directory.</para>
<para>
As an example, suppose you list the contents of the
directory and discover three architectures:
<filename>all</filename>, <filename>i586</filename>,
and <filename>qemux86</filename>.
Given this example, use the following commands:
<literallayout class='monospaced'>
smart channel &dash;&dash;add &lt;somealias&gt; type=rpm-md baseurl=http://server.name/rpm
smart channel &dash;&dash;add all type=rpm-md baseurl=http:server.name/rpm/all
smart channel &dash;&dash;add i585 type=rpm-md baseurl=http://server.name/rpm/i586
smart channel &dash;&dash;add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
</literallayout>
</para></listitem>
<listitem><para>
@ -3727,13 +3729,10 @@
</para></listitem>
</orderedlist>
</para>
</section>
<para>
After taking these steps and making sure that the other
requirements mentioned at the beginning of the section are met,
reboot the target device to take advantage of runtime package
installations.
</para>
<section id='runtime-package-management-ipk'>
<title>Using IPK</title>
<para>
If your packages are IPK, you can install packages onto an
@ -3750,6 +3749,7 @@
</literallayout>
</para>
</section>
</section>
<section id='testing-packages-with-ptest'>
<title>Testing Packages With ptest</title>