41067870c6
the idea is to blend in when no task is running, thus no background-color there. When tasks are running use the proxmox branding guideline dark-grey, it isn't used as often so it should fall into ones eye when changing but it has some use so it doesn't seems out of place. Reduce the border radius by a lot, so that it seems similar to the one our ExtJS theme uses for the buttons outside - the original border radius seems like it comes from the time where this was intended to be a floating badge, there it'd make sense but as integrated button one this seems to fit the style much more. Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
``rustup`` Toolchain
====================
We normally want to build with the ``rustc`` Debian package. To do that
you can set the following ``rustup`` configuration:
# rustup toolchain link system /usr
# rustup default system
Versioning of proxmox helper crates
===================================
To use current git master code of the proxmox* helper crates, add::
git = "ssh://gitolite3@proxdev.maurer-it.com/rust/proxmox"
or::
path = "../proxmox/proxmox"
to the proxmox dependency, and update the version to reflect the current,
pre-release version number (e.g., "0.1.1-dev.1" instead of "0.1.0").
Local cargo config
==================
This repository ships with a ``.cargo/config`` that replaces the crates.io
registry with packaged crates located in ``/usr/share/cargo/registry``.
A similar config is also applied building with dh_cargo. Cargo.lock needs to be
deleted when switching between packaged crates and crates.io, since the
checksums are not compatible.
To reference new dependencies (or updated versions) that are not yet packaged,
the dependency needs to point directly to a path or git source (e.g., see
example for proxmox crate above).