Lubuntu/livecd-rootfs
3
0
Fork 0
mirror of https://git.launchpad.net/livecd-rootfs synced 2025-12-12 06:33:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

be a bit more accurate about IMAGEFORMAT

Browse Source
This commit is contained in:
Michael Hudson-Doyle 2025-12-02 18:42:47 +13:00
parent 5e00e3ecb2
commit 65dad6ccc0
No known key found for this signature in database
GPG Key ID: 11DF4294CCA39893
1 changed files with 15 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.parameters
View File

@ -147,11 +147,21 @@ IMAGEFORMAT
----------- -----------
This is one of the more incoherently handled parameters. In rough This is one of the more incoherently handled parameters. In rough
outline it is the filesystem of the image we produce, but relatively outline it is the filesystem of the image we produce.
few builds produce raw images so _mostly_ it is set to 'plain' (which
causes live-build to just leave the rootfs as a directory tree) or Installer builds do not produce raw images, so this ends up being set
'none' (which causes live-build to do roughly the same thing but in a to 'plain' (which causes live-build to just leave the rootfs as a
different way?). directory tree) or 'none' (which causes live-build to do roughly the
same thing but in a different way?).
Image builds that use ubuntu-image set it to "ubuntu-image". These
builds do not call 'lb build' or 'lb binary'.
Other preinstalled images (mostly cpc images) set it to ext4 (but then
use live-build/ubuntu-cpc/hooks.d/remove-implicit-artifacts to remove
the output file that this causes live-build to produce...). Some
projects rely on this being set via metadata when building the project
it seems.
It can be set when starting an image build, but most builds do not and It can be set when starting an image build, but most builds do not and
the behavior when it is not set explicitly is pretty confusing. the behavior when it is not set explicitly is pretty confusing.