Bug 9415

Summary: IMAGE_FSTYPES: split image type and compress format
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Robert Yang <liezhi.yang>
Component: deploymentAssignee: Robert Yang <liezhi.yang>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Undecided CC: randy.macleod, richard.purdie, ross.burton
Version: 2.2   
Target Milestone: 2.2 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Robert Yang 2016-04-07 10:02:55 UTC
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.
Comment 1 Richard Purdie 2016-04-09 07:21:54 UTC
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.