What's New In 2.1 - Revision history

Jefro: /* What's new in the Yocto Project 2.1 release */

2016-05-20T18:44:02Z

What's new in the Yocto Project 2.1 release

← Older revision		Revision as of 18:44, 20 May 2016
Line 3:		Line 3:
	The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build architecture as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [https://yoctoproject.org/documentation documentation].		The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build architecture as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [https://yoctoproject.org/documentation documentation].

	As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).		As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes and version upgrades in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

	== General ==		== General ==

Jefro: /* What's new in the Yocto Project 2.1 release */

2016-05-20T18:42:44Z

What's new in the Yocto Project 2.1 release

← Older revision		Revision as of 18:42, 20 May 2016
Line 1:		Line 1:
	= What's new in the Yocto Project 2.1 release =		= What's new in the Yocto Project 2.1 release =

	The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build ~~system~~ as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [https://yoctoproject.org/documentation documentation].		The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build architecture as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [https://yoctoproject.org/documentation documentation].

	As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).		As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

Jefro: /* What's new in the Yocto Project 2.1 release */

2016-05-20T18:39:45Z

What's new in the Yocto Project 2.1 release

← Older revision		Revision as of 18:39, 20 May 2016
Line 1:		Line 1:
	= What's new in the Yocto Project 2.1 release =		= What's new in the Yocto Project 2.1 release =

	The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [[https://yoctoproject.org/documentation documentation]].		The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [https://yoctoproject.org/documentation documentation].

	As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).		As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

Jefro: /* What's new in the Yocto Project 2.1 release */

2016-05-20T18:39:32Z

What's new in the Yocto Project 2.1 release

← Older revision		Revision as of 18:39, 20 May 2016
Line 1:		Line 1:
	= What's new in the Yocto Project 2.1 release =		= What's new in the Yocto Project 2.1 release =

	The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [[https://yoctoproject.org/documentation\|documentation].		The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [[https://yoctoproject.org/documentation documentation]].

	As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).		As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

Jefro: /* What's new in the Yocto Project 2.1 release */

2016-05-20T18:39:13Z

What's new in the Yocto Project 2.1 release

← Older revision		Revision as of 18:39, 20 May 2016
Line 1:		Line 1:
	= What's new in the Yocto Project 2.1 release =		= What's new in the Yocto Project 2.1 release =

	The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the ~~<a href="~~https://yoctoproject.org/documentation">documentation~~</a>~~.		The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the [[https://yoctoproject.org/documentation\|documentation].

	As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).		As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

Jefro at 18:38, 20 May 2016

2016-05-20T18:38:40Z

← Older revision		Revision as of 18:38, 20 May 2016
Line 1:		Line 1:
	= What's new in the Yocto Project 2.1 release =		= What's new in the Yocto Project 2.1 release =

	As with most Yocto Project releases, the ~~Yocto Project~~ 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).		The Yocto Project has released version 2.1 of the OpenEmbedded build architecture, which includes BitBake, the Openembedded Core metadata layer, and other layers. We distribute this release as a reference distribution called Poky, which is used as a validation tool and starting point for others. Poky includes the OE build system as well as several other tools, metadata layers, scripts, and documentation, everything you need as a starting point for configuring and creating your own custom distribution. For more information, please see the <a href="https://yoctoproject.org/documentation">documentation</a>.

			As with most Yocto Project releases, the 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

	== General ==		== General ==

Jefro at 23:37, 16 May 2016

2016-05-16T23:37:29Z

← Older revision		Revision as of 23:37, 16 May 2016
Line 1:		Line 1:
	~~{\| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"~~
	~~\|This page is a draft - needs more screenshots and possibly copy-editing.'''~~
	\|}

	= What's new in the Yocto Project 2.1 release =		= What's new in the Yocto Project 2.1 release =

	As with most Yocto Project releases, the Yocto Project 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release) ~~but attempts to give an overview of the most visible improvements~~.		As with most Yocto Project releases, the Yocto Project 2.1 "krogoth" release comes with a large number of changes in different areas. If one were to try to extract a general theme for 2.1 however it would probably be cleaning out the dusty corners of the system, as well as finishing off some functionality that has been a long time in the making. This guide attempts to give an overview of the most visible improvements, though it doesn't cover all changes (in fact, it doesn't cover the hundreds of bugfixes and minor tweaks made since the last release).

	== General ==		== General ==

PaulEggleton: Typo/grammar fixes

2016-05-09T04:00:07Z

Typo/grammar fixes

← Older revision		Revision as of 04:00, 9 May 2016
Line 63:		Line 63:
	* '''Upgraded to Django 1.8.x from 1.6.x''': Django 1.8 has been designated as a Long Term Support release, with extended support until at least April 2018.		* '''Upgraded to Django 1.8.x from 1.6.x''': Django 1.8 has been designated as a Long Term Support release, with extended support until at least April 2018.
	* '''Improved build statistics data:''' following changes to buildstats, Toaster now provides a more accurate measure of Disk I/O per task, and displays both system and user CPU time.		* '''Improved build statistics data:''' following changes to buildstats, Toaster now provides a more accurate measure of Disk I/O per task, and displays both system and user CPU time.
	* '''~~Fix~~ date filters for builds:''' ensure you can retrieve a subset of builds by specifying a date range.		* '''Fixed date filters for builds:''' ensure you can retrieve a subset of builds by specifying a date range.
	* '''Show PROVIDES information in recipe dependencies:''' Toaster now identifies recipe build dependencies satisfied via the PROVIDES variable.		* '''Show PROVIDES information in recipe dependencies:''' Toaster now identifies recipe build dependencies satisfied via the PROVIDES variable.
	<gallery>		<gallery>
Line 71:		Line 71:
	File:Multiple-release-support.png\|Support for building two stable releases		File:Multiple-release-support.png\|Support for building two stable releases
	File:Improved_build_stats.png\|Improved build statistics data		File:Improved_build_stats.png\|Improved build statistics data
	File:Filter_by_date.png\|Date ~~filers~~ for builds		File:Filter_by_date.png\|Date filters for builds
	File:Provides_info.png\|PROVIDES information for recipe dependencies		File:Provides_info.png\|PROVIDES information for recipe dependencies
	</gallery>		</gallery>

PaulEggleton: Tweak eudev item

2016-05-09T03:50:12Z

Tweak eudev item

← Older revision		Revision as of 03:50, 9 May 2016
Line 49:		Line 49:
	* '''libav has been replaced by ffmpeg'''. Again, most of the major Linux distributions have made this move already - for some background see [https://lwn.net/Articles/650816/ this article from LWN].		* '''libav has been replaced by ffmpeg'''. Again, most of the major Linux distributions have made this move already - for some background see [https://lwn.net/Articles/650816/ this article from LWN].

	* '''udev has been replaced by eudev''' - for those still using SysV init (which is still the default) an update of the standalone udev was required as part of support for the Linux kernel 4.4 upgrade. ~~The~~ easiest course of action ~~here~~ turned out to be to migrate to the latest stable version of Gentoo's [https://wiki.gentoo.org/wiki/Eudev eudev] fork.		* '''udev has been replaced by eudev''' - for those still using SysV init (which is still the default) an update of the standalone udev was required as part of support for the Linux kernel 4.4 upgrade. Since udev is now part of systemd, the easiest course of action for continued SysV init support turned out to be to migrate to the latest stable version of Gentoo's [https://wiki.gentoo.org/wiki/Eudev eudev] fork.

	* The first step in moving towards the changing the default of the expand parameter in '''d.getVar()''' from False to True has been made by removing the default and making the parameter mandatory. This will force specifying the value; in a future release once layer maintainers have had a chance to adapt, a default of True will be set up.		* The first step in moving towards the changing the default of the expand parameter in '''d.getVar()''' from False to True has been made by removing the default and making the parameter mandatory. This will force specifying the value; in a future release once layer maintainers have had a chance to adapt, a default of True will be set up.

PaulEggleton: Fix minor grammar issue

2016-05-09T03:47:49Z

Fix minor grammar issue

← Older revision		Revision as of 03:47, 9 May 2016
Line 23:		Line 23:
	Added an '''npm module fetcher''' to BitBake and corresponding support class in OE-Core (requires separate nodejs recipe). Because of the way npm fetches dependencies as part of its operation, it was previously difficult to write reliable recipes for npm recipes - modules were fetched on the fly and outside of the do_fetch task, leading to problems with reproducibility as well as the inability to work behind a network proxy.		Added an '''npm module fetcher''' to BitBake and corresponding support class in OE-Core (requires separate nodejs recipe). Because of the way npm fetches dependencies as part of its operation, it was previously difficult to write reliable recipes for npm recipes - modules were fetched on the fly and outside of the do_fetch task, leading to problems with reproducibility as well as the inability to work behind a network proxy.

	'''Switching PREFERRED_PROVIDER to another virtual/* ~~providers~~ now results in old files being removed''' from the sysroot; earlier this would likely result in "The recipe <recipe> is trying to install files into a shared area when those files already exist" errors, requiring either explicit cleanup or simply deleting TMPDIR and restarting the build.		'''Switching PREFERRED_PROVIDER to another virtual/* provider now results in old files being removed''' from the sysroot; earlier this would likely result in "The recipe <recipe> is trying to install files into a shared area when those files already exist" errors, requiring either explicit cleanup or simply deleting TMPDIR and restarting the build.

	The runqemu script for more easily starting the QEMU system emulator gained support for qcow2 and vdi images, as well as images produced by the wic tool.		The runqemu script for more easily starting the QEMU system emulator gained support for qcow2 and vdi images, as well as images produced by the wic tool.