summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-classes.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-02 09:09:15 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-04 14:13:44 +0100
commit4ce46de598ffbafad6dae91e814ab6168e9654a9 (patch)
tree32f35fe648b509f2501cadee32c280cf3a91ffd8 /documentation/ref-manual/ref-classes.xml
parent10da562f611289ed6f938e89afcabcc90a6c9010 (diff)
downloadast2050-yocto-poky-4ce46de598ffbafad6dae91e814ab6168e9654a9.zip
ast2050-yocto-poky-4ce46de598ffbafad6dae91e814ab6168e9654a9.tar.gz
ref-manual: Added Smart-enabled package feed info to section.
There are steps the user can take to create a host-resident package feed (repository) whose front-end is Smart. The setup allows the user to install packages from the host feed during runtime on the target. The changes I made now include that fact. I also reformatted into a list some of the RPM limitations and benefits as they now numbered such that I could list them out as such. (From yocto-docs rev: bb733ec59c9275071ff5ff017adc52073d4dcef8) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-classes.xml')
-rw-r--r--documentation/ref-manual/ref-classes.xml52
1 files changed, 33 insertions, 19 deletions
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 7e01b4a..36f72b8 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -330,12 +330,12 @@
<para>
The package class you choose can affect build-time performance and has space
ramifications.
- In general, building a package with RPM takes about thirty percent more time as
- compared to using IPK to build the same or similar package.
- This comparison takes into account a complete build of the package with all
- dependencies previously built.
- The reason for this discrepancy is because the RPM package manager creates and
- processes more
+ In general, building a package with IPK takes about thirty percent less
+ time as compared to using RPM to build the same or similar package.
+ This comparison takes into account a complete build of the package with
+ all dependencies previously built.
+ The reason for this discrepancy is because the RPM package manager
+ creates and processes more
<ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> than the
IPK package manager.
Consequently, you might consider setting <filename>PACKAGE_CLASSES</filename>
@@ -343,22 +343,36 @@
</para>
<para>
- Keep in mind, however, that RPM starts to provide more abilities than IPK due to
- the fact that it processes more metadata.
- For example, this information includes individual file types, file checksum generation
- and evaluation on install, sparse file support, conflict detection and resolution
- for Multilib systems, ACID style upgrade, and repackaging abilities for rollbacks.
- </para>
-
- <para>
- Another consideration for packages built using the RPM package manager is space.
- For smaller systems, the extra space used for the Berkley Database and the amount
- of metadata can affect your ability to perform on-device upgrades.
+ Before making your decision on package manager, however, you should
+ consider some further things about using RPM:
+ <itemizedlist>
+ <listitem><para>
+ RPM starts to provide more abilities than IPK due to
+ the fact that it processes more metadata.
+ For example, this information includes individual file types,
+ file checksum generation and evaluation on install, sparse file
+ support, conflict detection and resolution for Multilib systems,
+ ACID style upgrade, and repackaging abilities for rollbacks.
+ </para></listitem>
+ <listitem><para>
+ For smaller systems, the extra space used for the Berkley
+ Database and the amount of metadata when using RPM can affect
+ your ability to perform on-device upgrades.
+ </para></listitem>
+ <listitem><para>
+ If you take the steps to set up a repository (package feed)
+ on the development host that can be used by Smart, you can
+ install packages from the feed while you are running the image
+ on the target (i.e. runtime installation of packages).
+ For information on how to set up this repository, see the
+ "NEED LINK" section in the Yocto Project Development Manual.
+ </para></listitem>
+ </itemizedlist>
</para>
<para>
- You can find additional information on the effects of the package class at these
- two Yocto Project mailing list links:
+ You can find additional information on the effects of the package
+ class at these two Yocto Project mailing list links:
<itemizedlist>
<listitem><para><ulink url='&YOCTO_LISTS_URL;/pipermail/poky/2011-May/006362.html'>
https://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html</ulink></para></listitem>
OpenPOWER on IntegriCloud