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
@@ -3628,10 +3628,6 @@
You have a web server, such as Apache 2,
installed and configured on the development host.
-
- You have createrepo installed on
- the development host.
-
You enable package management on the target by
listing "package-management" in the
@@ -3641,20 +3637,23 @@
-
- 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:
-
+
+ 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:
+
<VirtualHost *:80>
....
Alias /rpm ~/poky/build/tmp/deploy/rpm
@@ -3662,93 +3661,94 @@
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
-
-
-
- Change your working directory to
- tmp/deploy/rpm in the
- Build Directory.
-
-
- Create the repository data on the host using
- this command:
-
- createrepo .
-
-
-
-
- If you're updating, add
- ‐‐update to save some time.
-
-
-
- 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:
-
+
+
+
+ Run BitBake on package-index
+ on the host
+
+ 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 .
-
-
-
- On the target machine, add the repository to Smart.
- For somealias, provide a local
- alias for the repository:
-
- smart channel ‐‐add <somealias> type=rpm-md baseurl=http://server.name/rpm
-
-
-
- Also from the target machine, fetch the repository
- information using this command:
-
+
+
+
+ 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.
+
+ As an example, suppose you list the contents of the
+ directory and discover three architectures:
+ all, i586,
+ 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 i585 type=rpm-md baseurl=http://server.name/rpm/i586
+ smart channel ‐‐add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
+
+
+
+ Also from the target machine, fetch the repository
+ information using this command:
+
smart update
-
-
-
-
+
+
+
+
+
-
- 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.
-
+
+ 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:
-
+
+ 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
-
-
+
+
+