adamwill commented on the pull-request: `workstation: build with osbuild` that you are
following:
``
we usually capitalize the elements of the name, I think - e.g. Fedora-Workstation-Live ,
Fedora-Cloud-Base-Vagrant . It's not really important, but it'd just be a bit
inconsistent for this to be lower case.
What I'm concerned about is what the productmd properties of the image wind up as. If
it has the exact same subvariant, type and format as the 'real' Workstation live
that's an issue, because that's the triplet of identifying features that fedfind
and all the things built off it (mainly my openQA industrial complex, but also a few other
things I think) use to 'identify' images.
If the "image type" that's written into the productmd metadata is instead
"live-installer" (as this change *seems like* it might result in), that causes a
different problem: that is not a valid image type according to productmd -
https://github.com/release-engineering/productmd/blob/master/productmd/im... .
But in fact, looking at the pungi code, it almost seems like the image type in the
productmd metadata might *actually* be set to "dvd" - I think that's what
https://pagure.io/pungi/blob/master/f/pungi/phases/osbuild.py#_249 does - which is weird
in a *third* way, because the "dvd" image type is meant to indicate a
traditional DVD installer image, like the Fedora Server DVD.
I think the way I'd ideally *want* this to work is that we add a new image type to
productmd, "live-osbuild" or "osbuild-live" or something like that,
and have that be the type used in the productmd metadata for these images.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/1190