Bug 6640 - Customise BitBake and layer versions in a project
Summary: Customise BitBake and layer versions in a project
Status: RESOLVED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard: GUI design pending
Depends on:
Blocks:
 
Reported: 2014-08-21 11:18 UTC by Belen Barros Pena
Modified: 2018-10-04 12:40 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2014-08-21 11:18:57 UTC
When a Toaster project is created, your "Release" selection in the project creation process specifies a certain repository and version of BitBake to be used, and a set of layers from layer sources. In the 1.7 version of Toaster, there is no way to customise those values set against the selected "Release", apart from creating a new "Release" definition in a configuration file.

Users should be able to customise those values from the Toaster interface.
Comment 1 Belen Barros Pena 2014-08-21 12:06:49 UTC
From Alex:


On 21/08/2014 12:38, "Damian, Alexandru" <alexandru.damian@intel.com> wrote:

I'm gonna try to summarize my thoughts here.


Maybe we should define a "Release" as

- a release is a default template for populating project settings

once a project is created, any change in the project settings may be performed, without affecting the original template;

The bitbake version is part of the "release", and part of the project settings;
Comment 2 Michael Halstead 2015-08-12 15:58:07 UTC
Clearing 2.0 milestone
Comment 3 David Reyna 2018-10-04 12:40:59 UTC
The current fixture model covers this, where the lastest two stable branches are offered, plus master and local.