summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-09-26 14:16:36 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-10-01 22:52:54 +0100
commitd8d58411887762f993492cb14642334a59b03a03 (patch)
tree36d611544e1c873af44fc69d18f9c2b144c6e53f /documentation
parentec84110a74f75689ba82629e1710228e34f0b009 (diff)
downloadpoky-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>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml190
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 7ab10df483..bc78a08adc 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3629,10 +3629,6 @@
3629 installed and configured on the development host. 3629 installed and configured on the development host.
3630 </para></listitem> 3630 </para></listitem>
3631 <listitem><para> 3631 <listitem><para>
3632 You have <filename>createrepo</filename> installed on
3633 the development host.
3634 </para></listitem>
3635 <listitem><para>
3636 You enable package management on the target by 3632 You enable package management on the target by
3637 listing "package-management" in the 3633 listing "package-management" in the
3638 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></ulink> 3634 <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></ulink>
@@ -3641,20 +3637,23 @@
3641 </itemizedlist> 3637 </itemizedlist>
3642 </para> 3638 </para>
3643 3639
3644 <para> 3640 <section id='runtime-package-management-deb-rpm'>
3645 Following are the steps to set up the optional repository. 3641 <title>Using DEB and RPM</title>
3646 This example assumes you are using RPM and the Apache 2 3642
3647 server: 3643 <para>
3648 <orderedlist> 3644 Following are the steps to set up the optional repository.
3649 <listitem><para> 3645 This example assumes you are using RPM and the Apache 2
3650 Add the directory to your Apache configuration, which 3646 server:
3651 you can find at 3647 <orderedlist>
3652 <filename>/etc/httpd/conf/httpd.conf</filename>. 3648 <listitem><para>
3653 Use commands similar to these on the development system. 3649 Add the directory to your Apache configuration, which
3654 These example commands assume a top-level 3650 you can find at
3655 <link linkend='source-directory'>Source Directory</link> 3651 <filename>/etc/httpd/conf/httpd.conf</filename>.
3656 named <filename>poky</filename> in your home directory: 3652 Use commands similar to these on the development system.
3657 <literallayout class='monospaced'> 3653 These example commands assume a top-level
3654 <link linkend='source-directory'>Source Directory</link>
3655 named <filename>poky</filename> in your home directory:
3656 <literallayout class='monospaced'>
3658 &lt;VirtualHost *:80&gt; 3657 &lt;VirtualHost *:80&gt;
3659 .... 3658 ....
3660 Alias /rpm ~/poky/build/tmp/deploy/rpm 3659 Alias /rpm ~/poky/build/tmp/deploy/rpm
@@ -3662,93 +3661,94 @@
3662 Options +Indexes 3661 Options +Indexes
3663 &lt;/Directory&gt; 3662 &lt;/Directory&gt;
3664 &lt;/VirtualHost&gt; 3663 &lt;/VirtualHost&gt;
3665 </literallayout> 3664 </literallayout>
3666 </para></listitem> 3665 </para></listitem>
3667 <listitem><para> 3666 <listitem><para>
3668 Reload the Apache configuration as follows. 3667 Reload the Apache configuration as follows.
3669 For all commands, be sure you have root privileges. 3668 For all commands, be sure you have root privileges.
3670 </para> 3669 </para>
3671 <para> 3670 <para>
3672 If your development system is using Fedora or 3671 If your development system is using Fedora or
3673 CentOS, use the following: 3672 CentOS, use the following:
3674 <literallayout class='monospaced'> 3673 <literallayout class='monospaced'>
3675 service httpd reload 3674 service httpd reload
3676 </literallayout> 3675 </literallayout>
3677 For Ubuntu and Debian, use the following: 3676 For Ubuntu and Debian, use the following:
3678 <literallayout class='monospaced'> 3677 <literallayout class='monospaced'>
3679 /etc/init.d/apache2 reload 3678 /etc/init.d/apache2 reload
3680 </literallayout> 3679 </literallayout>
3681 For OpenSUSE, use the following: 3680 For OpenSUSE, use the following:
3682 <literallayout class='monospaced'> 3681 <literallayout class='monospaced'>
3683 /etc/init.d/apache2 reload 3682 /etc/init.d/apache2 reload
3684 </literallayout> 3683 </literallayout>
3685 </para></listitem> 3684 </para></listitem>
3686 <listitem><para> 3685 <listitem><para>
3687 Change your working directory to 3686 Run BitBake on <filename>package-index</filename>
3688 <filename>tmp/deploy/rpm</filename> in the 3687 on the host
3689 <link linkend='build-directory'>Build Directory</link>. 3688 <literallayout class='monospaced'>
3690 </para></listitem> 3689 bitbake package-index
3691 <listitem><para> 3690 </literallayout>
3692 Create the repository data on the host using 3691 </para></listitem>
3693 this command: 3692 <listitem><para>
3694 <literallayout class='monospaced'> 3693 Change your working directory to
3695 createrepo . 3694 <filename>tmp/deploy/rpm</filename> in the
3696 </literallayout> 3695 <link linkend='build-directory'>Build Directory</link>.
3697 </para> 3696 </para></listitem>
3698 <para> 3697 <listitem><para>
3699 <note> 3698 If you are using Security-Enhanced Linux (SELinux),
3700 If you're updating, add 3699 you need to label the files as being accessible
3701 <filename>&dash;&dash;update</filename> to save some time. 3700 through Apache.
3702 </note> 3701 Use the following command from the development host:
3703 </para></listitem> 3702 <literallayout class='monospaced'>
3704 <listitem><para>
3705 If you are using Security-Enhanced Linux (SELinux),
3706 you need to label the files as being accessible
3707 through Apache.
3708 Use the following command from the development host:
3709 <literallayout class='monospaced'>
3710 chcon -R -h -t httpd_sys_content_t . 3703 chcon -R -h -t httpd_sys_content_t .
3711 </literallayout> 3704 </literallayout>
3712 </para></listitem> 3705 </para></listitem>
3713 <listitem><para> 3706 <listitem><para>
3714 On the target machine, add the repository to Smart. 3707 On the target machine, add the repository to Smart
3715 For <filename>somealias</filename>, provide a local 3708 for every package architecture.
3716 alias for the repository: 3709 To see the list of package architectures, just list
3717 <literallayout class='monospaced'> 3710 the contents of the directory.</para>
3718 smart channel &dash;&dash;add &lt;somealias&gt; type=rpm-md baseurl=http://server.name/rpm 3711 <para>
3719 </literallayout> 3712 As an example, suppose you list the contents of the
3720 </para></listitem> 3713 directory and discover three architectures:
3721 <listitem><para> 3714 <filename>all</filename>, <filename>i586</filename>,
3722 Also from the target machine, fetch the repository 3715 and <filename>qemux86</filename>.
3723 information using this command: 3716 Given this example, use the following commands:
3724 <literallayout class='monospaced'> 3717 <literallayout class='monospaced'>
3718 smart channel &dash;&dash;add all type=rpm-md baseurl=http:server.name/rpm/all
3719 smart channel &dash;&dash;add i585 type=rpm-md baseurl=http://server.name/rpm/i586
3720 smart channel &dash;&dash;add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
3721 </literallayout>
3722 </para></listitem>
3723 <listitem><para>
3724 Also from the target machine, fetch the repository
3725 information using this command:
3726 <literallayout class='monospaced'>
3725 smart update 3727 smart update
3726 </literallayout> 3728 </literallayout>
3727 </para></listitem> 3729 </para></listitem>
3728 </orderedlist> 3730 </orderedlist>
3729 </para> 3731 </para>
3732 </section>
3730 3733
3731 <para> 3734 <section id='runtime-package-management-ipk'>
3732 After taking these steps and making sure that the other 3735 <title>Using IPK</title>
3733 requirements mentioned at the beginning of the section are met,
3734 reboot the target device to take advantage of runtime package
3735 installations.
3736 </para>
3737 3736
3738 <para> 3737 <para>
3739 If your packages are IPK, you can install packages onto an 3738 If your packages are IPK, you can install packages onto an
3740 existing running system by first sharing the 3739 existing running system by first sharing the
3741 <filename>tmp/deploy/ipk/</filename> directory 3740 <filename>tmp/deploy/ipk/</filename> directory
3742 through a web server and then by changing 3741 through a web server and then by changing
3743 <filename>/etc/opkg/base-feeds.conf</filename> 3742 <filename>/etc/opkg/base-feeds.conf</filename>
3744 to point at the shared server. 3743 to point at the shared server.
3745 Following is an example: 3744 Following is an example:
3746 <literallayout class='monospaced'> 3745 <literallayout class='monospaced'>
3747 $ src/gz all http://www.mysite.com/somedir/deploy/ipk/all 3746 $ src/gz all http://www.mysite.com/somedir/deploy/ipk/all
3748 $ src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a 3747 $ src/gz armv7a http://www.mysite.com/somedir/deploy/ipk/armv7a
3749 $ src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard 3748 $ src/gz beagleboard http://www.mysite.com/somedir/deploy/ipk/beagleboard
3750 </literallayout> 3749 </literallayout>
3751 </para> 3750 </para>
3751 </section>
3752 </section> 3752 </section>
3753 3753
3754 <section id='testing-packages-with-ptest'> 3754 <section id='testing-packages-with-ptest'>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-01 22:59:52 +0000