Open waynr opened 8 months ago
I am definitely not opposed to it, and as a maintainer of a large chunk of those downstream dependencies I don't mind either. It seems like those definitions already have some traction, so it sounds like it would mutually beneficial. The main requirement is that all the types are spec compliant. It looks like they are, but so long as they are, I wouldn't have an objection to using those types instead.
@flavio should weigh in as well as he is the other active maintainer here
I welcome this proposal!
Yep, that would be a fine place to start
Howdy! I've been working on implementing the server side of the distribution spec lately and have found https://github.com/containers/oci-spec-rs super useful in interpreting image and index manifests, descriptors, and manifest configs. The types match up to the spec definitions pretty well and even cover some territory missing in this repo's types.
My suggestion is to consider switching over to
oci-spec
in a future breaking changes release. I would even consider performing this refactor myself if the maintainers are open to it (and potentially some of the downstream dependencies if that makes the suggestion more palatable).The reason I'm interested in this is that I have a couple future tools in mind that I think would benefit from the compatibility offered by shared types. For example:
oci-distribution
to create implementations of these traits that enables my registry to act as a pull through cache, or even to duplicate content to downstream registries.Anyway, let me know if this is a contribution you'd be interested in in the future!