mirror of
https://git.proxmox.com/git/proxmox
synced 2025-08-06 06:32:36 +00:00
5f5a5194de
this is only used for CLI synopsis/usage strings, the API viewer already prints the full type text in a correct format. the old variant was also rather misleading, since on the CLI we don't pass in an array, but each item as its own parameter. noticed this while working on the pull/sync filtering series, but it affects quite a lot of stuff, among other things the Updater and Deleteable CLI, e.g. from `man proxmox-backup-manager`: > --delete <array> > List of properties to delete. vs. > --delete disable|validation-delay > List of properties to delete. But some of them might only have <string> as the item type text, which is not much nicer but also not really worse. The whole "List of .." is confusing anyway, but not easily solvable, since the description is used for - API dump/viewer (where it is a list/array of ..) - usage message/man pages (where it's a parameter that gives a single element, but it might be passed in multiple times to construct an array) Also, for some common occurrences, the item description is too generic, and it's not possible to override the description for external types with the current api macro. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com> [ Thomas: Added more context that was in the diffstat of the path ] Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> |
||
|---|---|---|
| .cargo | ||
| proxmox | ||
| proxmox-api-macro | ||
| proxmox-http | ||
| proxmox-sortable-macro | ||
| .gitignore | ||
| build.sh | ||
| Cargo.toml | ||
| Makefile | ||
| README.rst | ||
| rustfmt.toml | ||
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`.