openembedded-core.git/meta/classes/image-vm.bbclass, branch morty

Remove RM_OLD_IMAGE, it's no longer useful

2016-10-15T08:48:28+00:00

Since the move to put image deployment under sstate control in
d54339d4b1a7e884de636f6325ca60409ebd95ff old images are automatically
removed before a new image is deployed (the default behaviour of the
sstate logic).

RM_OLD_IMAGE is therefore no longer required to provide this
behaviour, remove the variable and its users.

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton

image: Deploy images to IMGDEPLOYDIR

2016-09-03T23:05:12+00:00

Changed deployment directory from DEPLOY_DIR_IMAGE to
IMGDEPLOYDIR to make sstate machinery to do final deployment and
generate manifest.

Renamed variable deploy_dir to deploy_dir_image in selftest code
to avoid confusion with DEPLOYDIR variable.

Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable
as it's now used as a new deployment destination.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

image-vm.bbclass: remove old images if RM_OLD_IMAGE is enabled

2016-08-20T15:05:28+00:00

[YOCTO #10164]

Signed-off-by: Jonathan Liu 
Signed-off-by: Richard Purdie

image-live, image-vm, wic: Remove fs size workaround

2016-06-03T12:12:14+00:00

Since mtools has been patched to live with filesystems with sizes
not divisible by sectors-per-track, we no longer need to try to
set the size based on our guess of the sectors-per-track dosfstools is
going to use.

Signed-off-by: Jussi Kukkonen 
Signed-off-by: Richard Purdie

classes/image_vm: allow different filesystems to be used for VM images.

2016-05-09T07:03:58+00:00

This allows for things like btrfs to be used vs just ext4.
The default value of ext4 is kept so there is no functional
change unless VM_ROOTFS_TYPE is set in the inherting recipe.

Signed-off-by: Ian Reinhart Geiser 
Signed-off-by: Ross Burton

image-vm.bbclass/image_types.bbclass: IMAGE_NAME -> IMAGE_LINK_NAME

2016-04-09T06:53:19+00:00

If we create hdddirect in the first time, and run bitbake to create
vmimg in the second time, then the previouse created
${IMAGE_LINK_NAME}.hdddirect may can not be found since it contains the
data string which are different. Use IMAGE_LINK_NAME to fix the problem.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

image-vm: Exclude DISK_SIGNATURE_GENERATED from task signature

2016-04-03T14:51:10+00:00

Otherwise the task hash changes between server and worker context
leading to changing task checksums.

Signed-off-by: Richard Purdie

image-vm.bbclass: remove invalid code

2016-03-31T12:22:55+00:00

It has been done in syslinux.bbclass.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

image-live.bbclass/image-vm.bbclass: remove duplicated code

2016-03-31T12:22:55+00:00

Move the common code to live_vm_common.bbclass and remove duplicated ones.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

bootimg.bbclass: merge it into image-live.bbclass

2016-03-31T12:22:50+00:00

They are doing the same things: create live images, merge them into one
bbclass makes it easy to understand.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie