FutureMigrationGuide/2.2 - Revision history

Joshua Lock: Point out that this page is an archive

2016-11-07T13:54:27Z

Point out that this page is an archive

← Older revision		Revision as of 13:54, 7 November 2016
Line 1:		Line 1:
	{\| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"		{\| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
	\|This ~~page should be used to keep track~~ of ~~items~~ which ~~should be added to~~ the ~~migration guide~~. ~~It's a living document for~~ the ~~life of a~~ development ~~cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.~~		\|This is an archived version of notes regarding changes which were mentioned in the Yocto Project 2.2/Morty Future Migration Guide. For the current development release please update [[FutureMigrationGuide]].

	~~Once the migration guide for a~~ release ~~has been completed the contents of this page should be archived in a versioned subpage (i.e.~~ [[FutureMigrationGuide~~/2.2~~]])
	\|}		\|}

Joshua Lock: Joshua Lock moved page FutureMigrationGuide to FutureMigrationGuide/2.2 without leaving a redirect: Archive morty/2.2 FutureMigrationGuide

2016-11-07T13:52:12Z

Joshua Lock moved page FutureMigrationGuide to FutureMigrationGuide/2.2 without leaving a redirect: Archive morty/2.2 FutureMigrationGuide

← Older revision	Revision as of 13:52, 7 November 2016
(No difference)

PaulEggleton at 06:28, 13 October 2016

2016-10-13T06:28:20Z

← Older revision		Revision as of 06:28, 13 October 2016
Line 6:		Line 6:

	=2.2 Migration Guide items=		=2.2 Migration Guide items=
	* The mimimum kernel version is now 3.2.0, due to the upgrade to glibc 2.24. Specifically for aarch64-based targets it is 3.14, and nios2-based targets 3.19.		* The mimimum kernel version is now 3.2.0, due to the upgrade to glibc 2.24. Specifically for aarch64-based targets it is 3.14, and nios2-based targets 3.19. Note: for x86/x86_64, OLDEST_KERNEL can be re-set to anything down to 2.6.32 if desired.
	* How we stage directories in sysroot has been simplified and introduces some new variables (SYSROOT_DIRS, SYSROOT_DIRS_NATIVE, SYSROOT_DIRS_BLACKLIST). See the v2 patch series on the OE-Core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121365.html		* How we stage directories in sysroot has been simplified and introduces some new variables (SYSROOT_DIRS, SYSROOT_DIRS_NATIVE, SYSROOT_DIRS_BLACKLIST). See the v2 patch series on the OE-Core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121365.html
	* Removal of old images and other files under tmp/deploy/ is now enabled by default due to a new staging method used for those files. As a consequence RM_OLD_IMAGE is now redundant.		* Removal of old images and other files under tmp/deploy/ is now enabled by default due to a new staging method used for those files. As a consequence RM_OLD_IMAGE is now redundant.

PaulEggleton: Add a bunch more migration items for 2.2

2016-10-13T05:46:55Z

Add a bunch more migration items for 2.2

@@ Line 6: / Line 6: @@
 =2.2 Migration Guide items=
 * How we stage directories in sysroot has been simplified and introduces some new variables (SYSROOT_DIRS, SYSROOT_DIRS_NATIVE, SYSROOT_DIRS_BLACKLIST). See the v2 patch series on the OE-Core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121365.html
 * bitbake now requires python 3.4+
-* the metadata now requires to use python3 syntax. There are many python3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.
+* The metadata now requires to use Python 3 syntax. There are many Python 3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.
-* most target python recipes have now been switched to Python 3, unfortunately systems using RPM as a package manager and providing online package-manager support via SMART still require Python 2
+* Most target python recipes have now been switched to Python 3, unfortunately systems using RPM as a package manager and providing online package-manager support via SMART still require Python 2
 * Uclibc removed in favour of musl
-* ${B} no longer the default working directory for tasks
+* ${B} is no longer the default working directory for tasks, so any custom tasks you define now need to either have the dirs varflag set
-* We require a UTF-8 locale on the build host. As C.UTF-8 isn't a standard we default to en_US.UTF-8
+* We require a UTF-8 locale on the build host due to Python 3. As C.UTF-8 isn't a standard we default to en_US.UTF-8
 * runqemu ported to Python and changes behaviour in some cases (NEEDS docs)

Joshua Lock: /* 2.2 Migration Guide items */ Note runqemu change

2016-09-02T15:57:14Z

2.2 Migration Guide items: Note runqemu change

← Older revision		Revision as of 15:57, 2 September 2016
Line 13:		Line 13:
	* ${B} no longer the default working directory for tasks		* ${B} no longer the default working directory for tasks
	* We require a UTF-8 locale on the build host. As C.UTF-8 isn't a standard we default to en_US.UTF-8		* We require a UTF-8 locale on the build host. As C.UTF-8 isn't a standard we default to en_US.UTF-8
			* runqemu ported to Python and changes behaviour in some cases (NEEDS docs)

Joshua Lock: /* 2.2 Migration Guide items */ mention forcing en_US.UTF-8

2016-08-03T16:15:36Z

2.2 Migration Guide items: mention forcing en_US.UTF-8

← Older revision		Revision as of 16:15, 3 August 2016
Line 12:		Line 12:
	* Uclibc removed in favour of musl		* Uclibc removed in favour of musl
	* ${B} no longer the default working directory for tasks		* ${B} no longer the default working directory for tasks
			* We require a UTF-8 locale on the build host. As C.UTF-8 isn't a standard we default to en_US.UTF-8

PaulEggleton at 23:49, 26 July 2016

2016-07-26T23:49:29Z

← Older revision		Revision as of 23:49, 26 July 2016
Line 10:		Line 10:
	* the metadata now requires to use python3 syntax. There are many python3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.		* the metadata now requires to use python3 syntax. There are many python3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.
	* most target python recipes have now been switched to Python 3, unfortunately systems using RPM as a package manager and providing online package-manager support via SMART still require Python 2		* most target python recipes have now been switched to Python 3, unfortunately systems using RPM as a package manager and providing online package-manager support via SMART still require Python 2
			* Uclibc removed in favour of musl
			* ${B} no longer the default working directory for tasks

Joshua Lock: /* 2.2 Migration Guide items */ mention smart python2 dependency, could be more nicely worded

2016-07-07T15:13:06Z

2.2 Migration Guide items: mention smart python2 dependency, could be more nicely worded

← Older revision		Revision as of 15:13, 7 July 2016
Line 9:		Line 9:
	* bitbake now requires python 3.4+		* bitbake now requires python 3.4+
	* the metadata now requires to use python3 syntax. There are many python3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.		* the metadata now requires to use python3 syntax. There are many python3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.
			* most target python recipes have now been switched to Python 3, unfortunately systems using RPM as a package manager and providing online package-manager support via SMART still require Python 2

Rpurdie: /* 2.2 Migration Guide items */

2016-06-02T07:27:57Z

2.2 Migration Guide items

← Older revision		Revision as of 07:27, 2 June 2016
Line 7:		Line 7:
	=2.2 Migration Guide items=		=2.2 Migration Guide items=
	* How we stage directories in sysroot has been simplified and introduces some new variables (SYSROOT_DIRS, SYSROOT_DIRS_NATIVE, SYSROOT_DIRS_BLACKLIST). See the v2 patch series on the OE-Core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121365.html		* How we stage directories in sysroot has been simplified and introduces some new variables (SYSROOT_DIRS, SYSROOT_DIRS_NATIVE, SYSROOT_DIRS_BLACKLIST). See the v2 patch series on the OE-Core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121365.html
			* bitbake now requires python 3.4+
			* the metadata now requires to use python3 syntax. There are many python3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note are subprocess command line pipes needing locale decoding, the syntax for octal values changed, the iter*() functions changed name, iterators now return views, not lists and some python modules changed names.

Joshua Lock: New page to track migration guide items for the next release. Add sysroot_stage_dirs changes for 2.2

2016-05-12T09:00:06Z

New page to track migration guide items for the next release. Add sysroot_stage_dirs changes for 2.2

New page

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the migration guide. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be archived in a versioned subpage (i.e. [[FutureMigrationGuide/2.2]])
|}

=2.2 Migration Guide items=
* How we stage directories in sysroot has been simplified and introduces some new variables (SYSROOT_DIRS, SYSROOT_DIRS_NATIVE, SYSROOT_DIRS_BLACKLIST). See the v2 patch series on the OE-Core mailing list: http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121365.html