diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 9b6711558e..8082a5499e 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -5969,6 +5969,136 @@ id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81'>commit message. +
+ <filename>SERIAL_CONSOLE</filename> Deprecated + + + The + SERIAL_CONSOLE + variable has been functionally replaced by the + SERIAL_CONSOLES + variable for some time. + With the Yocto Project 2.6 release, + SERIAL_CONSOLE has been officially deprecated. + + + + SERIAL_CONSOLE will continue to work as + before for the 2.6 release. + However, for the sake of future compatibility, it is recommended + that you replace all instances of + SERIAL_CONSOLE with + SERIAL_CONSOLES. + + The only difference in usage is that + SERIAL_CONSOLES expects entries to be + separated using semicolons as compared to + SERIAL_CONSOLE, which expects spaces. + + +
+ +
+ Configure Script Reports Unknown Options as Errors + + + If the configure script reports an unknown option, this now + triggers a QA error instead of a warning. + Any recipes that previously got away with specifying such unknown + options now need to be fixed. + +
+ +
+ Override Changes + + + The following changes have occurred: + + + The virtclass-native and + virtclass-nativesdk Overrides Have + Been Removed: + The virtclass-native and + virtclass-nativesdk overrides have + been deprecated since 2012 in favor of + class-native and + class-nativesdk, respectively. + Both virtclass-native and + virtclass-nativesdk are now dropped. + + The virtclass-multilib- overrides + for multilib are still valid. + + + + The forcevariable + Override Now Has a Higher Priority Than + libc Overrides: + The forcevariable override is + documented to be the highest priority override. + However, due to a long-standing quirk of how + OVERRIDES + is set, the libc overrides (e.g. + libc-glibc, + libc-musl, and so forth) erroneously + had a higher priority. + This issue is now corrected. + + It is likely this change will not cause any + problems. + However, it is possible with some unusual configurations + that you might see a change in behavior if you were + relying on the previous behavior. + Be sure to check how you use + forcevariable and + libc-* overrides in your custom + layers and configuration files to ensure they make sense. + + + The build-${BUILD_OS} + Override Has Been Removed: + The build-${BUILD_OS}, which is + typically build-linux, override has + been removed because building on a host operating system + other than a recent version of Linux is neither supported + nor recommended. + Dropping the override avoids giving the impression that + other host operating systems might be supported. + + + +
+ +
+ <filename>systemd</filename> Configuration is Now Split Into <filename>systemd-conf</filename> + + + The configuration for the systemd recipe + has been moved into a system-conf recipe. + Moving this configuration to a separate recipe avoids the + systemd recipe from becoming machine-specific + for cases where machine-specific configurations need to be applied + (e.g. for qemu* machines). + + + + Currently, the new recipe packages the following files: + + ${sysconfdir}/machine-id + ${sysconfdir}/systemd/coredump.conf + ${sysconfdir}/systemd/journald.conf + ${sysconfdir}/systemd/logind.conf + ${sysconfdir}/systemd/system.conf + ${sysconfdir}/systemd/user.conf + + If you previously used BitBake append files to append the + systemd recipe to change any of the + listed files, you must do so for the + systemd-conf recipe instead. + +
+
Automatic Testing Changes @@ -6023,16 +6153,26 @@ id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81'>commit message. BitBake Changes - The "_remove" operator now preserves whitespace. - Consequently, when specifying list items to remove, be aware - that leading and trailing whitespace resulting from the - removal is retained. - + The following BitBake changes occurred: + + + The "_remove" operator now preserves whitespace. + Consequently, when specifying list items to remove, be + aware that leading and trailing whitespace resulting from + the removal is retained. - - See the - "Removal (Override Style Syntax)" - section in the BitBake User Manual for a detailed example. + See the + "Removal (Override Style Syntax)" + section in the BitBake User Manual for a detailed example. + + + The server logfile + bitbake-cookerdaemon.log is now always + placed in the + Build Directory + instead of the current directory. + +
@@ -6056,6 +6196,92 @@ id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81'>commit message. errors. + +
+ Miscellaneous Changes + + + The following miscellaneous changes occurred: + + + Default to using the Thumb-2 instruction set for armv7a + and above. + If you have any custom recipes that build software that + needs to be built with the ARM instruction set, change the + recipe to set the instruction set as follows: + + ARM_INSTRUCTION_SET = "arm" + + + + run-postinsts no longer uses + /etc/*-postinsts for + dpkg/opkg in favor of built-in + postinst support. + + RPM behavior remains unchanged. + + + + The NOISO and + NOHDD variables are no longer used. + You now control building *.iso and + *.hddimg image types directly + by using the + IMAGE_FSTYPES + variable. + + + The scripts/contrib/mkefidisk.sh + has been removed in favor of Wic. + + + kernel-modules has been removed from + RRECOMMENDS + for qemumips and + qemumips64 machines. + Removal also impacts the x86-base.inc + file. + + genericx86 and + genericx86-64 retain + kernel-modules as part of the + RRECOMMENDS variable setting. + + + + The LGPLv2_WHITELIST_GPL-3.0 + variable has been removed. + If you are setting this variable in your configuration, + set or append it to the + WHITELIST_GPL-3.0 variable instead. + + + ${ASNEEDED} is now included in + the + TARGET_LDFLAGS + variable directly. + The remaining definitions from + meta/conf/distro/include/as-needed.inc + have been moved to corresponding recipes. + + + Support for DSA host keys has been dropped from the + OpenSSH recipes. + If you are still using DSA keys, you must switch over to a + more secure algorithm as recommended by the OpenSSH + upstream. + + + The dhcp recipe now uses the + dhcpd6.conf configuration file in + dhcpd6.service for IPv6 DHCP rather + than re-using dhcpd.conf, which is + now reserved for IPv4. + + + +