diff options
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html | 73 |
1 files changed, 0 insertions, 73 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html deleted file mode 100644 index eb43660f9e..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/ref-classes-package.html +++ /dev/null | |||
| @@ -1,73 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>7.13. Packaging - package*.bbclass</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="The Yocto Project Reference Manual"> | ||
| 8 | <link rel="up" href="ref-classes.html" title="Chapter 7. Classes"> | ||
| 9 | <link rel="prev" href="ref-classes-packagegroup.html" title="7.12. Package Groups - packagegroup.bbclass"> | ||
| 10 | <link rel="next" href="ref-classes-kernel.html" title="7.14. Building kernels - kernel.bbclass"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="7.13. Packaging - package*.bbclass"> | ||
| 13 | <div class="titlepage"><div><div><h2 class="title" style="clear: both"> | ||
| 14 | <a name="ref-classes-package"></a>7.13. Packaging - <code class="filename">package*.bbclass</code> | ||
| 15 | </h2></div></div></div> | ||
| 16 | <p> | ||
| 17 | The packaging classes add support for generating packages from a build's | ||
| 18 | output. | ||
| 19 | The core generic functionality is in <code class="filename">package.bbclass</code>. | ||
| 20 | The code specific to particular package types is contained in various sub-classes such as | ||
| 21 | <code class="filename">package_deb.bbclass</code>, <code class="filename">package_ipk.bbclass</code>, | ||
| 22 | and <code class="filename">package_rpm.bbclass</code>. | ||
| 23 | Most users will want one or more of these classes. | ||
| 24 | </p> | ||
| 25 | <p> | ||
| 26 | You can control the list of resulting package formats by using the | ||
| 27 | <code class="filename"><a class="link" href="ref-variables-glos.html#var-PACKAGE_CLASSES" title="PACKAGE_CLASSES">PACKAGE_CLASSES</a></code> | ||
| 28 | variable defined in the <code class="filename">local.conf</code> configuration file, | ||
| 29 | which is located in the <code class="filename">conf</code> folder of the | ||
| 30 | <a class="link" href="../dev-manual/source-directory.html" target="_self">Source Directory</a>. | ||
| 31 | When defining the variable, you can specify one or more package types. | ||
| 32 | Since images are generated from packages, a packaging class is | ||
| 33 | needed to enable image generation. | ||
| 34 | The first class listed in this variable is used for image generation. | ||
| 35 | </p> | ||
| 36 | <p> | ||
| 37 | The package class you choose can affect build-time performance and has space | ||
| 38 | ramifications. | ||
| 39 | In general, building a package with RPM takes about thirty percent more time as | ||
| 40 | compared to using IPK to build the same or similar package. | ||
| 41 | This comparison takes into account a complete build of the package with all | ||
| 42 | dependencies previously built. | ||
| 43 | The reason for this discrepancy is because the RPM package manager creates and | ||
| 44 | processes more metadata than the IPK package manager. | ||
| 45 | Consequently, you might consider setting <code class="filename">PACKAGE_CLASSES</code> | ||
| 46 | to "package_ipk" if you are building smaller systems. | ||
| 47 | </p> | ||
| 48 | <p> | ||
| 49 | Keep in mind, however, that RPM starts to provide more abilities than IPK due to | ||
| 50 | the fact that it processes more metadata. | ||
| 51 | For example, this information includes individual file types, file checksum generation | ||
| 52 | and evaluation on install, sparse file support, conflict detection and resolution | ||
| 53 | for multilib systems, ACID style upgrade, and repackaging abilities for rollbacks. | ||
| 54 | </p> | ||
| 55 | <p> | ||
| 56 | Another consideration for packages built using the RPM package manager is space. | ||
| 57 | For smaller systems, the extra space used for the Berkley Database and the amount | ||
| 58 | of metadata can affect your ability to do on-device upgrades. | ||
| 59 | </p> | ||
| 60 | <p> | ||
| 61 | You can find additional information on the effects of the package class at these | ||
| 62 | two Yocto Project mailing list links: | ||
| 63 | </p> | ||
| 64 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
| 65 | <li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html" target="_self"> | ||
| 66 | https://lists.yoctoproject.org/pipermail/poky/2011-May/006362.html</a></p></li> | ||
| 67 | <li class="listitem"><p><a class="ulink" href="http://lists.yoctoproject.org/pipermail/poky/2011-May/006363.html" target="_self"> | ||
| 68 | https://lists.yoctoproject.org/pipermail/poky/2011-May/006363.html</a></p></li> | ||
| 69 | </ul></div> | ||
| 70 | <p> | ||
| 71 | </p> | ||
| 72 | </div></body> | ||
| 73 | </html> | ||