Chapter 5. Migrating to a Newer Yocto Project Release

Table of Contents

5.1. General Migration Considerations
5.2. Moving to the Yocto Project 1.3 Release
5.2.1. Local Configuration
5.2.2. Recipes
5.2.3. Linux Kernel Naming
5.3. Moving to the Yocto Project 1.4 Release
5.3.1. BitBake
5.3.2. Build Behavior
5.3.3. Proxies and Fetching Source
5.3.4. Custom Interfaces File (netbase change)
5.3.5. Remote Debugging
5.3.6. Variables
5.3.7. Target Package Management with RPM
5.3.8. Recipes Moved
5.3.9. Removals and Renames
5.4. Moving to the Yocto Project 1.5 Release
5.4.1. Host Dependency Changes
5.4.2. atom-pc Board Support Package (BSP)
5.4.3. BitBake
5.4.4. QA Warnings
5.4.5. Directory Layout Changes
5.4.6. Shortened Git SRCREV Values
5.4.7. IMAGE_FEATURES
5.4.8. /run
5.4.9. Removal of Package Manager Database Within Image Recipes
5.4.10. Images Now Rebuild Only on Changes Instead of Every Time
5.4.11. Task Recipes
5.4.12. BusyBox
5.4.13. Automated Image Testing
5.4.14. Build History
5.4.15. udev
5.4.16. Removed and Renamed Recipes
5.4.17. Other Changes
5.5. Moving to the Yocto Project 1.6 Release
5.5.1. archiver Class
5.5.2. Packaging Changes
5.5.3. BitBake
5.5.4. Changes to Variables
5.5.5. Directory Layout Changes
5.5.6. Package Test (ptest)
5.5.7. Build Changes
5.5.8. qemu-native
5.5.9. core-image-basic
5.5.10. Licensing
5.5.11. CFLAGS Options
5.5.12. Custom Image Output Types
5.5.13. Tasks
5.5.14. update-alternative Provider
5.5.15. virtclass Overrides
5.5.16. Removed and Renamed Recipes
5.5.17. Removed Classes
5.5.18. Reference Board Support Packages (BSPs)
5.6. Moving to the Yocto Project 1.7 Release
5.6.1. Changes to Setting QEMU PACKAGECONFIG Options in local.conf
5.6.2. Minimum Git version
5.6.3. Autotools Class Changes
5.6.4. Binary Configuration Scripts Disabled
5.6.5. eglibc 2.19 Replaced with glibc 2.20
5.6.6. Kernel Module Autoloading
5.6.7. QA Check Changes
5.6.8. Removed Recipes
5.6.9. Miscellaneous Changes

This chapter provides information you can use to migrate work to a newer Yocto Project release. You can find the same information in the release notes for a given release.