diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-09-26 14:16:36 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-10-01 22:52:54 +0100 |
commit | d8d58411887762f993492cb14642334a59b03a03 (patch) | |
tree | 36d611544e1c873af44fc69d18f9c2b144c6e53f | |
parent | ec84110a74f75689ba82629e1710228e34f0b009 (diff) | |
download | ast2050-yocto-poky-d8d58411887762f993492cb14642334a59b03a03.zip ast2050-yocto-poky-d8d58411887762f993492cb14642334a59b03a03.tar.gz |
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>
-rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 190 |
1 files changed, 95 insertions, 95 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 7ab10df..bc78a08 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -3629,10 +3629,6 @@ 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 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></ulink> @@ -3641,20 +3637,23 @@ </itemizedlist> </para> - <para> - Following are the steps to set up the optional repository. - This example assumes you are using RPM and the Apache 2 - server: - <orderedlist> - <listitem><para> - Add the directory to your Apache configuration, which - you can find at - <filename>/etc/httpd/conf/httpd.conf</filename>. - Use commands similar to these on the development system. - These example commands assume a top-level - <link linkend='source-directory'>Source Directory</link> - named <filename>poky</filename> in your home directory: - <literallayout class='monospaced'> + <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 + server: + <orderedlist> + <listitem><para> + Add the directory to your Apache configuration, which + you can find at + <filename>/etc/httpd/conf/httpd.conf</filename>. + Use commands similar to these on the development system. + These example commands assume a top-level + <link linkend='source-directory'>Source Directory</link> + named <filename>poky</filename> in your home directory: + <literallayout class='monospaced'> <VirtualHost *:80> .... Alias /rpm ~/poky/build/tmp/deploy/rpm @@ -3662,93 +3661,94 @@ Options +Indexes </Directory> </VirtualHost> - </literallayout> - </para></listitem> - <listitem><para> - Reload the Apache configuration as follows. - For all commands, be sure you have root privileges. - </para> - <para> - If your development system is using Fedora or - CentOS, use the following: - <literallayout class='monospaced'> + </literallayout> + </para></listitem> + <listitem><para> + Reload the Apache configuration as follows. + For all commands, be sure you have root privileges. + </para> + <para> + If your development system is using Fedora or + CentOS, use the following: + <literallayout class='monospaced'> service httpd reload - </literallayout> - For Ubuntu and Debian, use the following: - <literallayout class='monospaced'> + </literallayout> + For Ubuntu and Debian, use the following: + <literallayout class='monospaced'> /etc/init.d/apache2 reload - </literallayout> - For OpenSUSE, use the following: - <literallayout class='monospaced'> + </literallayout> + For OpenSUSE, use the following: + <literallayout class='monospaced'> /etc/init.d/apache2 reload - </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>‐‐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 - through Apache. - Use the following command from the development host: - <literallayout class='monospaced'> + </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> + If you are using Security-Enhanced Linux (SELinux), + you need to label the files as being accessible + through Apache. + Use the following command from the development host: + <literallayout class='monospaced'> chcon -R -h -t httpd_sys_content_t . - </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: - <literallayout class='monospaced'> - smart channel ‐‐add <somealias> type=rpm-md baseurl=http://server.name/rpm - </literallayout> - </para></listitem> - <listitem><para> - Also from the target machine, fetch the repository - information using this command: - <literallayout class='monospaced'> + </literallayout> + </para></listitem> + <listitem><para> + 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 ‐‐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> + </para></listitem> + <listitem><para> + Also from the target machine, fetch the repository + information using this command: + <literallayout class='monospaced'> smart update - </literallayout> - </para></listitem> - </orderedlist> - </para> + </literallayout> + </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 - existing running system by first sharing the - <filename>tmp/deploy/ipk/</filename> directory - through a web server and then by changing - <filename>/etc/opkg/base-feeds.conf</filename> - to point at the shared server. - Following is an example: - <literallayout class='monospaced'> + <para> + If your packages are IPK, you can install packages onto an + existing running system by first sharing the + <filename>tmp/deploy/ipk/</filename> directory + through a web server and then by changing + <filename>/etc/opkg/base-feeds.conf</filename> + to point at the shared server. + Following is an example: + <literallayout class='monospaced'> $ src/gz all http://www.mysite.com/somedir/deploy/ipk/all $ src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a $ src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard - </literallayout> - </para> + </literallayout> + </para> + </section> </section> <section id='testing-packages-with-ptest'> |