Bug 4861

Summary: core-image-weston should not be in the base image combo box when poky-tiny is selected
Product: [Build System, Metadata & Runtime] Hob Reporter: Belen Barros Pena <belen.barros.pena>
Component: hobAssignee: Cristiana Voicu <cristiana.voicu>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: andreea.b.proca, belen.barros.pena, bluelightning, cristian.iorga, cristiana.voicu, jessica.zhang, poky.bs.watcher, poky.watcher, valentin.popa
Version: unspecified   
Target Milestone: 1.5 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Belen Barros Pena 2013-07-17 13:25:01 UTC
Steps to reproduce:

1. Launch Hob
2. Select a machine
3. Open the "Advanced configuration" dialog
4. Change your selected distro to "poky-tiny" and click "Save"

After recipe parsing, the base images available include core-image-weston, which you cannot build with poky-tiny. We need to take it out.

This brings back memories of bug 2565. There, we discussed how to enforce poky-tiny limitations in Hob. Paul Eggleton suggested to specify them in the distro configuration, but in the end we went for creating a hard-coded black list in Hob. Maintaining hard-coded black lists is a pain (as we can see from this bug report) so, should we reconsider Paul's approach?
Comment 1 Belen Barros Pena 2013-07-17 13:42:35 UTC
(In reply to comment #0)
> Steps to reproduce:
> 
> 1. Launch Hob
> 2. Select a machine
> 3. Open the "Advanced configuration" dialog
> 4. Change your selected distro to "poky-tiny" and click "Save"
> 
> After recipe parsing, the base images available include core-image-weston,
> which you cannot build with poky-tiny. We need to take it out.
> 
> This brings back memories of bug 2565. There, we discussed how to enforce
> poky-tiny limitations in Hob. Paul Eggleton suggested to specify them in the
> distro configuration, but in the end we went for creating a hard-coded black
> list in Hob. Maintaining hard-coded black lists is a pain (as we can see
> from this bug report) so, should we reconsider Paul's approach?

Cristiana just showed me this was implemented as Paul suggested. Sorry about the noise :(
Comment 3 Andreea Brandusa Proca 2013-07-22 12:36:55 UTC
Verified in master:31e6eee860b5f9f4ac9ef0889bcff5648de6e3f9.