proxmox-mirrors/proxmox
1
0
Fork 1
mirror of https://git.proxmox.com/git/proxmox synced 2025-08-13 06:01:25 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
470 Commits 3 Branches 0 Tags 17 MiB
Rust 99.7%
Makefile 0.2%
Shell 0.1%
176e208caf
Go to file
Wolfgang Bumiller 176e208caf api-macro: add consts for defaults 
Not sure how we want to actually handle default values yet.
For now we need to figure out what "feels best".
This adds default values as publicly available consts so
they can be accessed from anywhere as
`API_METHOD_<METHOD_NAME>_PARAM_DEFAULT_<PARAM_NAME>`.
This is quite a handful to type, but I'm not sure how to
make this better.

Within the function body we also have the
`api_get_default!(param_name)` macro which is more
convenient, but not available outside the `#[api]` tagged
function.

Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2020-03-23 09:15:54 +01:00
.cargo cargo: switch to use packaged crates by default 2020-01-03 09:39:52 +01:00
proxmox bump proxmox crate to 0.1.19-1 2020-03-19 10:00:50 +01:00
proxmox-api-macro api-macro: add consts for defaults 2020-03-23 09:15:54 +01:00
proxmox-sortable-macro build: switch to debcargo 2020-01-15 12:02:47 +01:00
.gitignore add Cargo.lock to .gitignore 2020-01-15 17:10:13 +01:00
build.sh build.sh: point to system compiler via rust-toolchain 2020-01-15 16:25:14 +01:00
Cargo.toml merge api, sys and tools into proxmox directly 2020-01-21 12:15:42 +01:00
Makefile buildsys: drop format check in check target 2020-03-16 12:21:14 +01:00
README.rst README: Remove 'Versioning', add 'Steps for Releases' 2020-01-15 14:26:06 +01:00
rustfmt.toml initial import, starting with vec & io helpers 2019-06-06 14:00:25 +02:00

README.rst 

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`.