Tycho Andersen

I generally like the idea, so thank you for doing this. A couple of thoughts: 1. it would be great if we could get rid of "aliases", e.g. _Window() has...

On Sun, Apr 05, 2020 at 11:05:22AM -0700, simboid wrote: > When I move/resize windows they lag/stutter really badly; sometimes if you really quickly either resize or move a floating...

> @tych0, could you elaborate a bit on your use case? Sure, I'm putting squashfs files in OCI images instead of gzipped tarballs, so I can direct mount them instead...

> I think in case of Skopeo, Skopeo itself is not consuming the image, and is used as a tool to pull those images; I think that's more the "distribution...

> e.g.implementations should / must produce an error if they're not able to "handle" / "process" a layer-type. That seems like a reasonable clarification to me!

What about just adding the clarification you already proposed above, i.e. > e.g.implementations should / must produce an error if they're not able to "handle" / "process" a layer-type. Doesn't...

I don't think case 1 you've provided is legal. Per https://github.com/opencontainers/image-spec/blob/master/manifest.md#image-manifest-property-descriptions we have, "The final filesystem layout MUST match the result of applying the layers to an empty directory." So...

> Which means that there's no way to have images that are compatible with both any of the existing runtimes and runtimes that support zstd. I don't think that's what...

> Can you elaborate on what other ways? Sure, but I don't think it's relevant for whether or not zstd support should be in the spec. With your proposed clarification,...

> IIUC) tools like skopeo should not be really affected for your specific use-case You'd think that, but it has broken before: https://github.com/containers/image/pull/801 Hence my concern about similar issues in...