9415 2016-04-07 10:02:55 +0000 IMAGE_FSTYPES: split image type and compress format 2016-04-09 07:21:54 +0000 1 1 7 Build System, Metadata & Runtime OE-Core deployment 2.2 x86 Multiple RESOLVED NOTABUG Undecided normal 2.2 M3 1 liezhi.yang liezhi.yang randy.macleod richard.purdie ross.burton --- --- Yes (doc changes required) oldest_to_newest 60896 0 liezhi.yang 2016-04-07 10:02:55 +0000 For example, currently, the IMAGE_FSTYPES are: jffs2 jffs2.sum \ cramfs \ ext2 ext2.gz ext2.bz2 ext2.lzma \ ext3 ext3.gz \ ext4 ext4.gz \ btrfs \ iso \ hddimg \ squashfs squashfs-xz squashfs-lzo \ ubi ubifs multiubi \ tar tar.gz tar.bz2 tar.xz tar.lz4 \ cpio cpio.gz cpio.xz cpio.lzma cpio.lz4 \ vmdk \ vdi \ qcow2 \ hdddirect \ elf \ wic wic.gz wic.bz2 wic.lzma \ " ext2, ext2.gz ext2.bz2 ext2.lzma can be divded into two part: image type: ext2 compress format: gz, bz2, lzma The similar to others, this can make things easier. In another world, make IMAGE_FSTYPES not contain compress format, and then once the user set the compress type, it can be compressed into any types. 60992 1 richard.purdie 2016-04-09 07:21:54 +0000 IMAGE_FSTYPES is a user visible control to select which outputs the user requires. It makes sense to allow the user to use the full type, including the compression type since in some cases a cpio/gz cmopressed initramfs may be wanted and a rootfs compressed with bz2 but you don't want a bz2 compressed initramfs or a gz compressed rootfs. I therefore believe we should not splut up IMAGE_FSTYPES.