Crates.io | depit |
lib.rs | depit |
version | 0.2.2 |
source | src |
created_at | 2023-04-07 11:46:57.622956 |
updated_at | 2023-04-11 11:02:26.11055 |
description | WIT dependency management |
homepage | |
repository | https://github.com/rvolosatovs/depit |
max_upload_size | |
id | 832884 |
size | 53,175 |
depit
is a simple WIT dependency manager binary and Rust library, which manages your wit/deps
. It's main objective is to ensure that whatever is located in your wit/deps
is consistent with your dependency manifest (default: wit/deps.toml
) and dependency lock (default: wit/deps.lock
).
A dependency manifest is a TOML-encoded table mapping dependency names to their source specifications. In it's simplest form, a source specification is a URL string of a gzipped tarball containing a directory tree with a wit
subdirectory containing wit
files.
Example:
# wit/deps.toml
http = "https://github.com/WebAssembly/wasi-http/archive/6c6855a7329fb040a48ecdbad1765be8e694416c.tar.gz"
io = "https://github.com/rvolosatovs/wasi-io/archive/v0.1.0.tar.gz"
logging = "https://github.com/WebAssembly/wasi-logging/archive/d106e59b25297d0496e6a5d221ad090e19c3aaa3.tar.gz"
poll = "https://github.com/WebAssembly/wasi-poll/archive/3ff76670b0d43bc7c8a224c2e65880a963416835.tar.gz"
random = "https://github.com/WebAssembly/wasi-random/archive/28970c50c3797c0087fa75a15e88bfa39b91e0a0.tar.gz"
A source specfication can also be a structure with the following fields:
url
- same format as the URL stringsha256
- (optional) hex-encoded sha256 digest of the contents of the URLsha512
(optional) hex-encoded sha512 digest of the contents of the URLExample:
# wit/deps.toml
[logging]
url = "https://github.com/WebAssembly/wasi-logging/archive/d106e59b25297d0496e6a5d221ad090e19c3aaa3.tar.gz"
sha256 = "4bb4aeab99e7323b30d107aab78e88b2265c1598cc438bc5fbc0d16bb63e798f"
sha512 = "13b52b59afd98dd4938e3a651fad631d41a2e84ce781df5d8957eded77a8e1ac4277e771a10225cd4a3a9eae369ed7e8fee6e26f9991a2caa7c97c4a758b1ae6"
Note, depit
assumes that it has full control over wit/deps
and so it may delete and modify contents of wit/deps
at any time!
Use depit
or depit lock
to populate wit/deps
using wit/deps.toml
manifest and wit/deps.lock
(will be created if it does not exist)
Use depit::lock!
macro in build.rs
of your project to automatically lock your wit/deps
.
See crate documentation for more advanced use cases
depit
is lazy by default and will only fetch/write when it absolutely has todepit
assumes that result of fetching from a URL is deterministic, that is contents returned by GET of a URL domain.com
must always return exactly the same contents. Note, that you can use sha256
or sha512
fields in your manifest entry to invalidate the cache in this case