MAN page from OpenSuSE cargo-1.43.1-12.1.x86_64.rpm

CARGO\-PACKAGE

Section: \ \& (1)
Updated: 2020-02-06
Index

NAME

cargo-package - Assemble the local package into a distributable tarball

SYNOPSIS

cargo package [OPTIONS]

DESCRIPTION

This command will create a distributable, compressed .crate file with thesource code of the package in the current directory. The resulting file willbe stored in the target/package directory. This performs the followingsteps:

1.Load and check the current workspace, performing some basic checks.

: *Path dependencies are not allowed unless they have a version key. Cargowill ignore the path key for dependencies in published packages.dev-dependencies do not have this restriction.

2.Create the compressed .crate file.

: *The original Cargo.toml file is rewritten and normalized.

: *[patch], [replace], and [workspace] sections are removed from themanifest.

: *Cargo.lock is automatically included if the package contains anexecutable binary or example target. cargo-install(1) will use thepackaged lock file if the --locked flag is used.

: *A .cargo_vcs_info.json file is included that contains informationabout the current VCS checkout hash if available (not included with--allow-dirty).

3.Extract the .crate file and build it to verify it can build.

: *This will rebuild your package from scratch to ensure that it can bebuilt from a pristine state. The --no-verify flag can be used to skipthis step.

: 4.Check that build scripts did not modify any source files.

The list of files included can be controlled with the include and excludefields in the manifest.

See https://doc.rust-lang.org/cargo/reference/publishing.html <L>the referencefor more details aboutpackaging and publishing.

OPTIONS

Package Options

-l, --list

: Print files included in a package without making one.

--no-verify

: Doncqt verify the contents by building them.

--no-metadata

: Ignore warnings about a lack of human-usable metadata (such as thedescription or the license).

--allow-dirty

: Allow working directories with uncommitted VCS changes to be packaged.

Compilation Options

--target TRIPLE

Package for the given architecture. The default is the hostarchitecture. The general format of the triple is<arch><sub>-<vendor>-<sys>-<abi>. Run rustc --print target-list for alist of supported targets.

This may also be specified with the build.targethttps://doc.rust-lang.org/cargo/reference/config.html <L>config value

Note that specifying this flag makes Cargo run in a different mode where thetarget artifacts are placed in a separate directory. See thehttps://doc.rust-lang.org/cargo/guide/build-cache.html <L>build cachedocumentation for more details.

--target-dir DIRECTORY

: Directory for all generated artifacts and intermediate files. May also bespecified with the CARGO_TARGET_DIR environment variable, or thebuild.target-dir https://doc.rust-lang.org/cargo/reference/config.html <L>config valueDefaultsto target in the root of the workspace.

Feature Selection

The feature flags allow you to control the enabled features for the "current"package. The "current" package is the package in the current directory, or theone specified in --manifest-path. If running in the root of a virtualworkspace, then the default features are selected for all workspace members,or all features if --all-features is specified.

When no feature options are given, the default feature is activated forevery selected package.

--features FEATURES

: Space or comma separated list of features to activate. These features onlyapply to the current directorycqs package. Features of direct dependenciesmay be enabled with <dep-name>/<feature-name> syntax. This flag may bespecified multiple times, which enables all specified features.

--all-features

: Activate all available features of all selected packages.

--no-default-features

: Do not activate the default feature of the current directorycqspackage.

Manifest Options

--manifest-path PATH

: Path to the Cargo.toml file. By default, Cargo searches for theCargo.toml file in the current directory or any parent directory.

--frozen, --locked

: Either of these flags requires that the Cargo.lock file isup-to-date. If the lock file is missing, or it needs to be updated, Cargo willexit with an error. The --frozen flag also prevents Cargo fromattempting to access the network to determine if it is out-of-date.
These may be used in environments where you want to assert that theCargo.lock file is up-to-date (such as a CI build) or want to avoid networkaccess.

--offline

Prevents Cargo from accessing the network for any reason. Without thisflag, Cargo will stop with an error if it needs to access the network andthe network is not available. With this flag, Cargo will attempt toproceed without the network if possible.

Beware that this may result in different dependency resolution than onlinemode. Cargo will restrict itself to crates that are downloaded locally, evenif there might be a newer version as indicated in the local copy of the index.See the cargo-fetch(1) command to download dependencies before goingoffline.

May also be specified with the net.offline https://doc.rust-lang.org/cargo/reference/config.html <L>config value

Miscellaneous Options

-j N, --jobs N

: Number of parallel jobs to run. May also be specified with thebuild.jobs https://doc.rust-lang.org/cargo/reference/config.html <L>config valueDefaults tothe number of CPUs.

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