Download OpenEmbedded User Manual

Chapter 8. Recipes
bitbake -b recipes/procps/procps_4.0.0.bb
This enables you to test, and fix the package manually without having bitbake automatically select it
normally.
By using this feature in conjunction with overrides you can also disable (or select) specific versions
based on the override. The following example from glibc shows that this version has been disabled for
the sh3 architecture because it doesn’t support sh3. This will force bitbake to try and select one of the
other available versions of glibc instead:
recipes/glibc/glibc_2.3.2+cvs20040726.bb:DEFAULT_PREFERENCE_sh3 = "-99"
8.26. Initscripts: How to handle daemons
This section is to be completed.
•
update-rc.d class
•
sh syntax
•
stop/stop/restart params
•
sample/standard script?
•
volatiles
8.27. Alternatives: How to handle the same command in
multiple packages
Alternatives are used when the same command is provided by multiple packages. A classic example is
busybox, which provides a whole set of commands such as /bin/ls and /bin/find, which are also provided
by other packages such as coreutils (/bin/ls) and findutils (/bin/find).
A system for handling alternatives is required to allow the user to choose which version of the command
they wish to have installed. It should be possible to install either one, or both, or remove one when both
are installed etc, and to have no issues with the packages overwriting files from other packages.
The most common reason for alternatives is to reduce the size of the binaries. By cutting down on
features, built in help, error messages and combining multiple binaries into one large binary it’s possible
to save considerable space. Often users are not expected to use the commands interactively in embedded
appliances and therefore these changes have no visible effect to the user. In some situations users may
have interactive access, or they may be more advanced users who want shell access on appliances that
90