cargo-artifact-dependency 0.4.1

Stable crate alternative for cargo artifact dependency.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

# cargo-artifact-dependency

Stable crate alternative for [cargo artifact dependency](https://doc.rust-lang.org/cargo/reference/unstable.html#artifact-dependencies).

> [!WARNING]
> This crate currently only supports binary artifacts. If you need other
> artifact types, please open an [issue on github](https://github.com/RoxyOS/cargo-artifact-dependency/issues).

## Why

Cargo artifact dependencies are still an unstable Cargo feature and may still
have bugs. This crate exists as a temporary alternative while artifact
dependency support remains unstable.

## Quick Start

```rust
use cargo_artifact_dependency::{ArtifactDependencyBuilder, BuildProfile};

fn main() -> Result<(), cargo_artifact_dependency::Error> {
    // Describe the ripgrep dependency and resolve its artifact.
    let artifact_path = ArtifactDependencyBuilder::default()
        .crate_name("ripgrep")
        .version("14")
        .bin_name("rg")
        .profile(BuildProfile::Release)
        .build()
        .unwrap()
        .resolve()?;

    // Use the resolved artifact path in your own workflow.
    println!("{}", artifact_path.display());
    Ok(())
}
```

## Notes

This crate does not emulate Cargo.toml's full `version + path` dependency
resolution semantics. If you need a local development path, you can gate `.path(...)`
behind a feature.

For example:

```rust
let mut builder = ArtifactDependencyBuilder::default()
    .crate_name("example")
    .version("0.1");

#[cfg(feature = "local-dev")]
{
    builder = builder.path("/absolute/path/to/example");
}
```