Yocto Project 1.3 Migration notes
| Note: this page is temporary until the release notes are generated. |
Local configuration
SSTATE_MIRRORS
The shared state cache as pointed to by SSTATE_DIR by default now has two-character subdirectories to prevent there being an issue with too many files in the same directory; also, native sstate packages will go into a subdirectory named using the distro ID string. If you copy the newly structured sstate cache to a mirror location (either local or remote) and then point to it in SSTATE_MIRRORS, you need to append "PATH" to the end of the mirror URL so that the path used by bitbake before the mirror substitution is appended to the path used to access the mirror. For example:
SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH"
bblayers.conf
The meta-yocto layer has been split into two parts - meta-yocto and meta-yocto-bsp, corresponding to the Poky reference distro configuration and the reference hardware BSPs respectively. When running bitbake or hob for the first time after upgrading, your conf/bblayers.conf will be updated to handle this change and you will be asked to re-run/restart for the changes to take effect.
Recipes
Python function whitespace
All python functions must now use four spaces for indentation. Previously we had an inconsistent mix of spaces and tabs, which made extending these functions using _append or _prepend complicated given that python treats whitespace as syntactically significant. If you are defining or extending any python functions (such as populate_packages, do_unpack, do_patch, etc.) in custom recipes or classes, you need to ensure you are using consistent four-space indentation.
proto= in SRC_URI
Any use of proto= in SRC_URI needs to be changed to protocol= - this particularly applies to svn://, bzr://, hg:// osc:// URIs; others were already using protocol= so this improves consistency.
Task recipes
"Task" recipes are now known as "Package groups" and have been renamed from task-*.bb to packagegroup-*.bb. Existing references to the previous task-* names should work in most cases and there is an automatic upgrade path for most packages, however you should update references in your own recipes and configuration as they may be removed in future releases. You should also rename any custom task-* recipes to packagegroup-*, and change them to inherit packagegroup instead of task, as well as taking the opportunity to remove anything now handled by packagegroup.bbclass, such as providing -dev and -dbg packages, setting LIC_FILES_CHKSUM, etc. See classes/packagegroup.bbclass for further details.
IMAGE_FEATURES
Image recipes that previously included "apps-console-core" in IMAGE_FEATURES should now include "splash" instead to enable the boot-up splash screen; apps-console-core will still include the splash screen but will generate a warning. The "apps-x11-core" and "apps-x11-games" IMAGE_FEATURES features have been removed.
Removed recipes
The following recipes have been removed. For most of them it is unlikely that you would have any references to them in your own metadata, but just in case they are listed here:
- libx11-trim: replaced by libx11 (negligible size difference with modern Xorg)
- xserver-xorg-lite: use xserver-xorg (negligible size difference with DRI and GLX modules not installed)
- xserver-kdrive: effectively unmaintained for many years
- mesa-xlib: no longer serves any purpose
- galago: replaced by telepathy
- gail: functionality was integrated into GTK+ 2.13
- eggdbus: no longer needed
- gcc-*-intermediate: build has been restructured to avoid the need for this step
- libgsmd: unmaintained for many years, ofono provided instead
- contacts, dates, tasks, eds-tools: largely unmaintained PIM application suite; has been moved to meta-gnome in meta-openembedded
