From 0d194a8c621006d3846f9fe3a756ce71a15f733a Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 27 Sep 2013 13:58:02 -0700 Subject: dev-manual, ref-manual: Review edits for new variables. Applied review changes to the following variables: IMAGE_NAME DATETIME SDK_ARCH IMAGE_BASENAME TUNE_PKGARCH PACKAGE_GROUP COMPLEMENTARY_GLOB BUSYBOX_SPLIT_SUID Also, reformatted some 1.5 package version requirements into a list rather than a lazy literallayout tag. Provided some new wording for the "Directory Layout Changes" section in the Migration chapter. (From yocto-docs rev: 60c3a905dd9212f1b4f6969341640a0726342d11) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../dev-manual/dev-manual-common-tasks.xml | 180 ++++++++++++--------- 1 file changed, 106 insertions(+), 74 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index bc78a08adc..fe34e8ecd8 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -3609,10 +3609,9 @@ Setting Up Runtime Package Management - For RPM, IPK, and DEB package formats, it is possible to set - up a repository that is a host-based - package feed from which you can install packages on the - target system during runtime. + For supported package formats, it is possible to set + up a repository that is a host-based package feed from which + you can install packages on the target system during runtime. Doing so is optional and depends on the following: @@ -3637,23 +3636,30 @@ -
- Using DEB and RPM - - - Following are the steps to set up the optional repository. - This example assumes you are using RPM and the Apache 2 - server: - - - Add the directory to your Apache configuration, which - you can find at - /etc/httpd/conf/httpd.conf. - Use commands similar to these on the development system. - These example commands assume a top-level - Source Directory - named poky in your home directory: - + + The following list provides steps for setting up the optional + repository regardless of the package format. + Once you work through these generic steps, see the + "Using RPM" + section or the + "Using IPK" + section for remaining steps specific to the package type. + + The example assumes you are using the Apache 2 server: + + + + Add the directory to your Apache configuration, which + you can find at + /etc/httpd/conf/httpd.conf. + Use commands similar to these on the development system. + These example commands assume a top-level + Source Directory + named poky in your home directory. + The example also assumes an RPM package type. + If you are using a different package type, such as + IPK, use "ipk" in the pathnames: + <VirtualHost *:80> .... Alias /rpm ~/poky/build/tmp/deploy/rpm @@ -3661,53 +3667,62 @@ Options +Indexes </Directory> </VirtualHost> - - - - Reload the Apache configuration as follows. - For all commands, be sure you have root privileges. - - - If your development system is using Fedora or - CentOS, use the following: - + + + + Reload the Apache configuration as follows. + For all commands, be sure you have root privileges. + + + If your development system is using Fedora or + CentOS, use the following: + service httpd reload - - For Ubuntu and Debian, use the following: - + + For Ubuntu and Debian, use the following: + /etc/init.d/apache2 reload - - For OpenSUSE, use the following: - + + For OpenSUSE, use the following: + /etc/init.d/apache2 reload - - - - Run BitBake on package-index - on the host - + + + + Re-generate the package index: + bitbake package-index - - - - Change your working directory to - tmp/deploy/rpm in the - Build Directory. - - - 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: - - chcon -R -h -t httpd_sys_content_t . - - + + + + 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. + Again, the example assumes RPM package types: + + chcon -R -h -t httpd_sys_content_t tmp/deploy/rpm + + + + + +
+ Using RPM + + + Following are RPM-specific steps needed for setting up the + optional repository. + Perform these steps after working through the common steps + at the start of this section: + 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. + To see the list of package architectures, list + the contents of the + setting-up-runtime-package-management tmp/deploy/rpm directory + on the host. As an example, suppose you list the contents of the directory and discover three architectures: @@ -3715,7 +3730,7 @@ and qemux86. Given this example, use the following commands: - smart channel ‐‐add all type=rpm-md baseurl=http:server.name/rpm/all + 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 @@ -3728,6 +3743,9 @@ + You can now use the smart query + and smart install commands to find + and install packages from the repositories.
@@ -3735,18 +3753,32 @@ Using IPK - If your packages are IPK, you can install packages onto an - existing running system by first sharing the - tmp/deploy/ipk/ directory - through a web server and then by changing - /etc/opkg/base-feeds.conf - to point at the shared server. - Following is an example: - - $ 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 - + Following are IPK-specific steps needed for setting up the + optional repository. + Perform these steps after working through the common steps + at the start of this section: + + Install packages onto an + existing running system by first sharing the + tmp/deploy/ipk/ directory + through a web server and then by changing + /etc/opkg/base-feeds.conf + to point at the shared server. + Following is an example: + + 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 + + From the target machine, fetch the + repository information using this command: + + opkg update + + + You can now use the opkg list and + opkg install commands to find and + install packages from the repositories.
-- cgit v1.2.3-54-g00ecf