Skip to content

Conversation

@jcgl17
Copy link
Contributor

@jcgl17 jcgl17 commented Nov 15, 2025

My attempt to close #3995. Writes the json manifest to /usr/lib/os-manifest. Maybe it's too presumptuous to claim that path, but naming is hard and I had to pick something.

Since the manifest takes up only ~300k with >2000 packages, compressing the manifest didn't seem to make sense.

@jcgl17
Copy link
Contributor Author

jcgl17 commented Nov 15, 2025

It's probably better to name this file something like mkosi-manifest instead of os-manifest. A more reasonable claim.

@behrmann
Copy link
Contributor

It's probably better to name this file something like mkosi-manifest instead of os-manifest. A more reasonable claim.

I'd prefer this to be mkosi-named, otherwise the name is too generic and similar to os-release and for something more general a UAPI spec would be more fitting that should then also take all the existing SBOM stuff into consideration, let's keep this localised to mkosi.

If json manifest is requested and metadata would not be cleaned due to
CleanPackageMetadata=, write the manifest to the OS image under the same
condition as when os-release would be written (i.e. not sysext, confext,
addon, or overlay).
@jcgl17
Copy link
Contributor Author

jcgl17 commented Nov 17, 2025

Sounds right to me. Just pushed a change to change from os-manifest to mkosi-manifest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Optionally include manifest in built image

2 participants