Ryan Levick (rylev) (Mar 19 2024 at 16:33): Ryan Levick (rylev) (Mar 19 2024 at 16:33):@Peter Huene I'd love a way to download a wit package from a registry into a local directory (resolving its deps into a deps folder) and rendering everything as wit files. Is that something you would imagine wit would gain the ability to do?
Yoshua Wuyts (Mar 19 2024 at 17:05):@Ryan Levick (rylev) what does: "and rendering everything as wit files." mean in this context?
Lann Martin (Mar 19 2024 at 17:08):Binary encodings of WIT don't include original file structure info; they are just a flat set of packages
Yoshua Wuyts (Mar 19 2024 at 17:08):ahh, okay okay
Lann Martin (Mar 19 2024 at 17:09):I'm thinking we could do wit/deps/namespace.package@version/package.wit, at least until we work out something for https://bytecodealliance.zulipchat.com/#narrow/stream/327223-wit-bindgen/topic/WIT.20directory.20structure
Ryan Levick (rylev) (Mar 19 2024 at 17:11):@Yoshua Wuyts and many tools expect human readable wit files (not to mention, it's better for humans, of course).
Yoshua Wuyts (Mar 19 2024 at 17:13):ahh, okay yeah I see!
Yoshua Wuyts (Mar 19 2024 at 17:13):ty
Lann Martin (Mar 19 2024 at 17:33):https://github.com/bytecodealliance/wasm-tools/issues/1461
Peter Huene (Mar 19 2024 at 18:23):I'm on leave today, but to answer the original question, certainly the wit tool should have some facility to render registry packages in a user-friendly format; if not recreating the original WIT source, something approximate
Last updated: Nov 25 2024 at 19:03 UTC