ab06665649
The `Updatable` trait is our mechanism for "updating" values. The `Updater` trait is a serde-helper to allow using `skip_serializing_if` on api type structs which `#[derive(Updater)]` All basic types implement `Updatable<Updater = Option<T>>`, and all `Option<T>` where `T: Updatable` are implicitly also updatable from `Option<T>`. With the update to the `#[api]` macro, all `#[api]` types will implicitly `#[derive(Updatable)]` via the default implementation (which simply assignes from an `Option<Self>`), unless they explicitly also `#[derive(Updater)]` in which case an implementation is derived which goes through each "field" found in the updater. To prevent fields from being updatable via an Updater `#[updater(fixed)]` can be used. Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
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.
Steps for Releases
==================
- Cargo.toml updates:
- Bump all modified crate versions.
- Update all the other crates' Cargo.toml to depend on the new versions if
required, then bump their version as well if not already done.
- Update debian/changelog files in all the crates updated above.
- Build packages with `make deb`.