MAN page from OpenSuSE cargo-1.36.0-lp151.5.4.2.x86_64.rpm
CARGO\-OWNER
Section: \ \& (1)
Updated: 2019-02-05
Index NAME
cargo-owner - Manage the owners of a crate on the registry
SYNOPSIS
cargo owner [OPTIONS] --add LOGIN [CRATE]
cargo owner [OPTIONS] --remove LOGIN [CRATE]
cargo owner [OPTIONS] --list [CRATE]
DESCRIPTION
This command will modify the owners for a crate on the registry. Owners of acrate can upload new versions and yank old versions. Non-team owners can alsomodify the set of owners, so take care!
This command requires you to be authenticated with either the --token optionor using cargo-login(1).
If the crate name is not specified, it will use the package name from thecurrent directory.
See https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner <L>the referencefor moreinformation about owners and publishing.
OPTIONS
Owner Options
-a, --add LOGIN...
- Invite the given user or team as an owner.
-r, --remove LOGIN...
- Remove the given user or team as an owner.
-l, --list
- List owners of a crate.
--token TOKEN
- API token to use when authenticating. This overrides the token stored inthe credentials file (which is created by cargo-login(1)).
https://doc.rust-lang.org/cargo/reference/config.html <L>Cargo configenvironment variables can beused to override the tokens stored in the credentials file. The token forcrates.io may be specified with the CARGO_REGISTRY_TOKEN environmentvariable. Tokens for other registries may be specified with environmentvariables of the form CARGO_REGISTRIES_NAME_TOKEN where NAME is the nameof the registry in all capital letters.
--index INDEX
- The URL of the registry index to use.
--registry REGISTRY
- Name of the registry to use. Registry names are defined in https://doc.rust-lang.org/cargo/reference/config.html <L>Cargo config filesIf not specified, the default registry is used, which is defined by theregistry.default config key which defaults to crates-io.
Display Options
-v, --verbose
- Use verbose output. May be specified twice for "very verbose" output whichincludes extra output such as dependency warnings and build script output.May also be specified with the term.verbosehttps://doc.rust-lang.org/cargo/reference/config.html <L>config value
-q, --quiet
- No output printed to stdout.
--color WHEN
- Control when colored output is used. Valid values:
- *auto (default): Automatically detect if color support is available on theterminal.
- *always: Always display colors.
- *never: Never display colors.
May also be specified with the term.colorhttps://doc.rust-lang.org/cargo/reference/config.html <L>config value
Common Options
-h, --help
- Prints help information.
-Z FLAG...
- Unstable (nightly-only) flags to Cargo. Run cargo -Z help fordetails.
ENVIRONMENT
See https://doc.rust-lang.org/cargo/reference/environment-variables.html <L>the referencefordetails on environment variables that Cargo reads.
EXIT STATUS
0
- Cargo succeeded.
101
- Cargo failed to complete.
EXAMPLES
- 1.List owners of a package:
cargo owner --list foo
- 2.Invite an owner to a package:
cargo owner --add username foo
- 3.Remove an owner from a package:
cargo owner --remove username foo
SEE ALSO
cargo(1), cargo-login(1), cargo-publish(1)
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- Owner Options
- Display Options
- Common Options
- ENVIRONMENT
- EXIT STATUS
- EXAMPLES
- SEE ALSO
This document was created byman2html,using the manual pages.
