summaryrefslogtreecommitdiffstats
path: root/documentation
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
parent10da562f611289ed6f938e89afcabcc90a6c9010 (diff)
downloadpoky-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')
-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 7e01b4ac05..36f72b85b0 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -330,12 +330,12 @@
330 <para> 330 <para>
331 The package class you choose can affect build-time performance and has space 331 The package class you choose can affect build-time performance and has space
332 ramifications. 332 ramifications.
333 In general, building a package with RPM takes about thirty percent more time as 333 In general, building a package with IPK takes about thirty percent less
334 compared to using IPK to build the same or similar package. 334 time as compared to using RPM to build the same or similar package.
335 This comparison takes into account a complete build of the package with all 335 This comparison takes into account a complete build of the package with
336 dependencies previously built. 336 all dependencies previously built.
337 The reason for this discrepancy is because the RPM package manager creates and 337 The reason for this discrepancy is because the RPM package manager
338 processes more 338 creates and processes more
339 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> than the 339 <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink> than the
340 IPK package manager. 340 IPK package manager.
341 Consequently, you might consider setting <filename>PACKAGE_CLASSES</filename> 341 Consequently, you might consider setting <filename>PACKAGE_CLASSES</filename>
@@ -343,22 +343,36 @@
343 </para> 343 </para>
344 344
345 <para> 345 <para>
346 Keep in mind, however, that RPM starts to provide more abilities than IPK due to 346 Before making your decision on package manager, however, you should
347 the fact that it processes more metadata. 347 consider some further things about using RPM:
348 For example, this information includes individual file types, file checksum generation 348 <itemizedlist>
349 and evaluation on install, sparse file support, conflict detection and resolution 349 <listitem><para>
350 for Multilib systems, ACID style upgrade, and repackaging abilities for rollbacks. 350 RPM starts to provide more abilities than IPK due to
351 </para> 351 the fact that it processes more metadata.
352 352 For example, this information includes individual file types,
353 <para> 353 file checksum generation and evaluation on install, sparse file
354 Another consideration for packages built using the RPM package manager is space. 354 support, conflict detection and resolution for Multilib systems,
355 For smaller systems, the extra space used for the Berkley Database and the amount 355 ACID style upgrade, and repackaging abilities for rollbacks.
356 of metadata can affect your ability to perform on-device upgrades. 356 </para></listitem>
357 <listitem><para>
358 For smaller systems, the extra space used for the Berkley
359 Database and the amount of metadata when using RPM can affect
360 your ability to perform on-device upgrades.
361 </para></listitem>
362 <listitem><para>
363 If you take the steps to set up a repository (package feed)
364 on the development host that can be used by Smart, you can
365 install packages from the feed while you are running the image
366 on the target (i.e. runtime installation of packages).
367 For information on how to set up this repository, see the
368 "NEED LINK" section in the Yocto Project Development Manual.
369 </para></listitem>
370 </itemizedlist>
357 </para> 371 </para>
358 372
359 <para> 373 <para>
360 You can find additional information on the effects of the package class at these 374 You can find additional information on the effects of the package
361 two Yocto Project mailing list links: 375 class at these two Yocto Project mailing list links:
362 <itemizedlist> 376 <itemizedlist>
363 <listitem><para><ulink url='&YOCTO_LISTS_URL;/pipermail/poky/2011-May/006362.html'> 377 <listitem><para><ulink url='&YOCTO_LISTS_URL;/pipermail/poky/2011-May/006362.html'>
364 https://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html</ulink></para></listitem> 378 https://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html</ulink></para></listitem>