Commit aad3305
committed
cmd/oci-image-tool/main.go: Add description with supported versions
This shows up in the --help output.
I expect image-tools to support a range of image-spec versions, not
just a single one. For example, once image-spec cuts 2.0, image-tools
should still be able to process 1.x images for some reasonable
deprecation period. image-spec is setting us up for that possibility
by using the v1 package for the Go types that are likely to change.
And SemVer means that if we can unpack a 1.3 image, we can also unpack
1.2, 1.1, and 1.0 images. So I think we want this to be printing:
* OCI Image Format Specification: 1.0.0-rc5
now. Once 1.0 is cut we should show:
* OCI Image Format Specification: 1.0.0
Once 1.1 is cut we should show our position in the 1.x series:
* OCI Image Format Specification: 1.1.0
And then when 2.0 is cut we should show our positions in both the 1.x
and 2.x series. If 2.0 happened after 1.1 (without a 1.2, etc.), that
would be:
* OCI Image Format Specification: 1.1.0, 2.0.0
I see less need to support multiple runtime-spec formats, since
they're only used in 'oci-image-tool create ...'. But the approach I
used for image-spec ports well to runtime-spec, so I've listed a
version for it too.
Signed-off-by: W. Trevor King <[email protected]>1 parent 144d945 commit aad3305
1 file changed
+3
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| 23 | + | |
| 24 | + | |
23 | 25 | | |
24 | 26 | | |
25 | 27 | | |
| |||
35 | 37 | | |
36 | 38 | | |
37 | 39 | | |
| 40 | + | |
38 | 41 | | |
39 | 42 | | |
40 | 43 | | |
| |||
0 commit comments