You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For our purposes, storing Flatpak metadata in labels in the OCI image is strictly better than annotations, because it allows compatibility with registries and other systems that can only handle docker v2 images, and not OCI images. We don't know any reason that annotations are practically better - it seems unlikely that label support will be dropped from any OCI-supporting system in the foreseeable future, even if annotations were designed as a label replacement.
The current development code tries to handle both annotations and labels, but that means that we need a flag at OCI bundle creation time and even less conveniently, we need a flag when adding a oci+https:// remote - currently done by using an URL ...?index=labels.
OCI's are not widely deployed, and in fact, the only place we need to worry about compatibility is when an older Flatpak client accesses Flatpaks from registry.fedoraproject.org. Given that, we could get considerable simplification by making Flatpak only generate and consume images with metadata in the labels, and handle compatibility Fedora-side, by:
Making the build system turn label-only Flatpaks into annotation+label Flatpaks
Making registry.fedoraproject.org server up two static indexes, one when the client asks for ?label:org.flatpak.ref:exists and one when the client asks for ?annotation:org.flatpak.ref:exists.
In those indexes, only include the Flatpak annotations when the client asks for annotations, and only include the Flatpak labels when the client asks for labels, to avoid doubling the index size.
The text was updated successfully, but these errors were encountered:
Instead of assuming that the source image has annotations, handle
the case where the source image only has labels as well. Our new
plan is that Flaptak 1.6 will break strict backwards compatibility
and only generate images with metadata in labels.
(See flatpak/flatpak#3192)
For our purposes, storing Flatpak metadata in labels in the OCI image is strictly better than annotations, because it allows compatibility with registries and other systems that can only handle docker v2 images, and not OCI images. We don't know any reason that annotations are practically better - it seems unlikely that label support will be dropped from any OCI-supporting system in the foreseeable future, even if annotations were designed as a label replacement.
The current development code tries to handle both annotations and labels, but that means that we need a flag at OCI bundle creation time and even less conveniently, we need a flag when adding a
oci+https://
remote - currently done by using an URL...?index=labels
.OCI's are not widely deployed, and in fact, the only place we need to worry about compatibility is when an older Flatpak client accesses Flatpaks from
registry.fedoraproject.org
. Given that, we could get considerable simplification by making Flatpak only generate and consume images with metadata in the labels, and handle compatibility Fedora-side, by:The text was updated successfully, but these errors were encountered: