Could you describe the "save a recipe off" in more detail? We are not understanding this point well.

(In reply to comment #1)
> Could you describe the "save a recipe off" in more detail? We are not
> understanding this point well.

If you change the types of IMAGES generated in hob this is saved globally. So if I select tar.gz tar.bz2 and tar.xz then for each image (core-image-sato, core-image-lsb-sdk, etc) I build within hob all these values are defined.

In reality this should be saved per custom image and not globally, so if I make recipes they should save the IMAGES_TYPES in the recipe:

hob-image-custom1: tar.gz
hob-image-custom2: tar.bz2
hob-image-custom3: tar.gz tar.bz2 tar.xz

In summary we need  to move setting IMAGE_FSTYPES from 'conf/hob-post.conf' to 'hob-image-customN.bb'

Hi, Matthew: 

I am currently looking at the design of the Hob settings, and I am just wondering if this feature has any impact in the GUI. 

Are you suggesting that the image types should be set per base image (i.e each of the base images available for selection in Hob should have a set of image types linked to it)?

Thanks,

Belen

(In reply to comment #3)
> Hi, Matthew: 
> 
> I am currently looking at the design of the Hob settings, and I am just
> wondering if this feature has any impact in the GUI. 
> 
> Are you suggesting that the image types should be set per base image (i.e
> each of the base images available for selection in Hob should have a set of
> image types linked to it)?
> 
> Thanks,
> 
> Belen

This does not need to effect the GUI. It just effects the saved .bb files. This myimage.bb file should have the IMAGE_FSTYPES and not the hob-{pre,post}.conf files.

That way if I make my own custom image with my own custom packages it also saves my own custom image type I selected as well.

-M

Relate to overal refactor of configuration changes for hob

At this point, work will take place on toaster, not hob so marking as won't fix.