Bug 9164

Summary: The toaster-custom-images layer should not show like any other layer, and should not be removable
Product: [Build System, Metadata & Runtime] Toaster Reporter: Belen Barros Pena <belen.barros.pena>
Component: toasterAssignee: Toaster default assignee <toaster>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: belen.barros.pena, david.reyna, jessica.zhang, jose.perez.carranza, stanciux.mihail
Version: 2.0   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard: GUI design available
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Design - The meta-custom-images layer none

Description Belen Barros Pena 2016-02-24 12:03:48 UTC 
The toaster-custom-images layer is the "special", Toaster-only layer that provides custom images created with Toaster. Currently, we are treating this layer like any other layer. In particular, we allow users to remove it from the project. 

We should probably not allow users to remove that layer from a project, otherwise things become rather odd. For example, right now, if you remove it, it will be added again the moment you create a custom image. You can also remove it and build existing custom images without problems. These differences in behaviour between normal layers and the toaster-custom-images layer are bound to confuse people.

The attached design document suggests how to deal with this layer.
Comment 1 Belen Barros Pena 2016-02-24 12:06:01 UTC 
Note that although the design document calls this layer "meta-custom-images", the current name (toaster-custom-images) should be perfectly fine.
Comment 2 Belen Barros Pena 2016-02-24 12:08:00 UTC 
Created attachment 3003 [details]
Design - The meta-custom-images layer