]>
Commit | Line | Data |
---|---|---|
1 | ``rustup`` Toolchain | |
2 | ==================== | |
3 | ||
4 | We normally want to build with the ``rustc`` Debian package. To do that | |
5 | you can set the following ``rustup`` configuration: | |
6 | ||
7 | # rustup toolchain link system /usr | |
8 | # rustup default system | |
9 | ||
10 | ||
11 | Versioning of proxmox helper crates | |
12 | =================================== | |
13 | ||
14 | To use current git master code of the proxmox* helper crates, add:: | |
15 | ||
16 | git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox" | |
17 | ||
18 | or:: | |
19 | ||
20 | path = "../proxmox/proxmox" | |
21 | ||
22 | to the proxmox dependency, and update the version to reflect the current, | |
23 | pre-release version number (e.g., "0.1.1-dev.1" instead of "0.1.0"). | |
24 | ||
25 | Local cargo config | |
26 | ================== | |
27 | ||
28 | This repository ships with a ``.cargo/config`` that replaces the crates.io | |
29 | registry with packaged crates located in ``/usr/share/cargo/registry``. | |
30 | ||
31 | A similar config is also applied building with dh_cargo. Cargo.lock needs to be | |
32 | deleted when switching between packaged crates and crates.io, since the | |
33 | checksums are not compatible. | |
34 | ||
35 | To reference new dependencies (or updated versions) that are not yet packaged, | |
36 | the dependency needs to point directly to a path or git source (e.g., see | |
37 | example for proxmox crate above). |