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
Richard Purdie
parent
ec84110a74
commit
d8d5841188
|
|
@ -3628,10 +3628,6 @@
|
||||||
You have a web server, such as Apache 2,
|
You have a web server, such as Apache 2,
|
||||||
installed and configured on the development host.
|
installed and configured on the development host.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>
|
|
||||||
You have <filename>createrepo</filename> installed on
|
|
||||||
the development host.
|
|
||||||
</para></listitem>
|
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
You enable package management on the target by
|
You enable package management on the target by
|
||||||
listing "package-management" in the
|
listing "package-management" in the
|
||||||
|
|
@ -3641,6 +3637,9 @@
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<section id='runtime-package-management-deb-rpm'>
|
||||||
|
<title>Using DEB and RPM</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Following are the steps to set up the optional repository.
|
Following are the steps to set up the optional repository.
|
||||||
This example assumes you are using RPM and the Apache 2
|
This example assumes you are using RPM and the Apache 2
|
||||||
|
|
@ -3683,24 +3682,18 @@
|
||||||
/etc/init.d/apache2 reload
|
/etc/init.d/apache2 reload
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para></listitem>
|
</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>
|
<listitem><para>
|
||||||
Change your working directory to
|
Change your working directory to
|
||||||
<filename>tmp/deploy/rpm</filename> in the
|
<filename>tmp/deploy/rpm</filename> in the
|
||||||
<link linkend='build-directory'>Build Directory</link>.
|
<link linkend='build-directory'>Build Directory</link>.
|
||||||
</para></listitem>
|
</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>‐‐update</filename> to save some time.
|
|
||||||
</note>
|
|
||||||
</para></listitem>
|
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
If you are using Security-Enhanced Linux (SELinux),
|
If you are using Security-Enhanced Linux (SELinux),
|
||||||
you need to label the files as being accessible
|
you need to label the files as being accessible
|
||||||
|
|
@ -3711,11 +3704,20 @@
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
On the target machine, add the repository to Smart.
|
On the target machine, add the repository to Smart
|
||||||
For <filename>somealias</filename>, provide a local
|
for every package architecture.
|
||||||
alias for the repository:
|
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'>
|
<literallayout class='monospaced'>
|
||||||
smart channel ‐‐add <somealias> type=rpm-md baseurl=http://server.name/rpm
|
smart channel ‐‐add all type=rpm-md baseurl=http:server.name/rpm/all
|
||||||
|
smart channel ‐‐add i585 type=rpm-md baseurl=http://server.name/rpm/i586
|
||||||
|
smart channel ‐‐add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
|
|
@ -3727,13 +3729,10 @@
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
</para>
|
</para>
|
||||||
|
</section>
|
||||||
|
|
||||||
<para>
|
<section id='runtime-package-management-ipk'>
|
||||||
After taking these steps and making sure that the other
|
<title>Using IPK</title>
|
||||||
requirements mentioned at the beginning of the section are met,
|
|
||||||
reboot the target device to take advantage of runtime package
|
|
||||||
installations.
|
|
||||||
</para>
|
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
If your packages are IPK, you can install packages onto an
|
If your packages are IPK, you can install packages onto an
|
||||||
|
|
@ -3750,6 +3749,7 @@
|
||||||
</literallayout>
|
</literallayout>
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
</section>
|
||||||
|
|
||||||
<section id='testing-packages-with-ptest'>
|
<section id='testing-packages-with-ptest'>
|
||||||
<title>Testing Packages With ptest</title>
|
<title>Testing Packages With ptest</title>
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue