tests: Dynamically generate containers

Currently we have a hardcoded "exampleos.tar" fixture, as well as two `.ociarchive` containers that also hardcode its content. Having pre-generated container fixtures on one hand is good because we're testing compatibility of import from a frozen format. But it also means that we can't easily test changing our output format. And I'd like to introduce some changes to the output format. I'll reintroduce compat testing another way. Add some internal code to extend an OCI directory.
ostreedev · Jan 6, 2022 · f08de47 · f08de47
1 parent c185409
commit f08de47
Show file tree

Hide file tree

Showing 10 changed files with 653 additions and 51 deletions.
diff --git a/lib/Cargo.toml b/lib/Cargo.toml
@@ -25,7 +25,7 @@ indicatif = "0.16.0"
 once_cell = "1.9"
 libc = "0.2.92"
 rustix = "0.31.3"
-oci-spec = "0.5.0"
+oci-spec = "0.5.3"
 openat = "0.1.20"
 openat-ext = "0.2.0"
 openssl = "0.10.33"

diff --git a/lib/src/container/mod.rs b/lib/src/container/mod.rs
@@ -218,7 +218,7 @@ mod encapsulate;
 pub use encapsulate::*;
 mod unencapsulate;
 pub use unencapsulate::*;
-mod ociwriter;
+pub(crate) mod ociwriter;
 mod skopeo;
 pub mod store;