Bug 8218 - Provide a way to update layer information from the Toaster GUI
Summary: Provide a way to update layer information from the Toaster GUI
Status: NEW
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 1.8
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Toaster default assignee
QA Contact:
URL:
Whiteboard: GUI design pending
Depends on:
Blocks:
 
Reported: 2015-08-27 13:08 UTC by Belen Barros Pena
Modified: 2023-12-14 04:28 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2015-08-27 13:08:06 UTC
Currently, layer information is imported from layer sources at set up time, and then the information can be updated with 

manage.py lsupdates

We should provide an easier way to update layer information: an option accessible from the GUI would be good.
Comment 1 Belen Barros Pena 2015-11-19 16:34:42 UTC
After some discussion, we decided the following:

* The information obtained through building a layer is likely to be more accurate than the information provided by the layer index

* The most useful outcome of updating your layer index information is the possibility of bringing in any new layers added to the layer index

So, when you update the layer index information, we will not touch anything if the layer already exists in the Toaster database, but we will add any new layers to the Toaster database. 

This is not perfect: if a recipe was added to an existing layer, I will not get that into Toaster (although the recipe will be added if I build the layer). But it seems a decent enough compromise.