CARGO-PKGID(1)

📦 version 1.92.0, in ubuntu resolute

✨ CARGO-PKGID(1) ✨

okay bestie, welcome to the cargo-pkgid page 💖 this one lives in Cargo's General Commands Manual and honestly? it's giving "small command, huge main character energy." Let's get into it.

🌸 NAME 🌸

cargo-pkgid — print a fully qualified package specification. That's it, that's the job, and it slays at it. 💅

🎀 SYNOPSIS 🎀

cargo pkgid [options] [spec]

🦋 DESCRIPTION 🦋

So here's the vibe: you hand it a spec argument, and it prints out the fully qualified package ID specifier for a package or dependency in the current workspace. Iconic. ✨

But heads up — if spec is ambiguous about which package it's referring to in the dependency graph, this command will straight up error out. No guessing games, no vibes-based resolution. 😭

And if you don't give it a spec at all? Then it just prints the specifier for the local package. Chill. Easy. Done.

Also, lowkey important: this command requires that a lockfile is available and that dependencies have been fetched. No lockfile, no pkgid. Periodt.

A package specifier is made of three things: a name, a version, and a source URL. The cute part is you're allowed to use partial specifiers to succinctly match a specific package — as long as it matches exactly one package. Only one, bestie. That's the rule. 🫶

This same specifier format is also used by other parts in Cargo, like cargo-metadata(1) and the JSON messages emitted by Cargo (https://doc.rust-lang.org/cargo/reference/external-tools.html#json-messages).

The format of a spec can be one of the following:

The specification grammar can be found in chapter Package ID Specifications: https://doc.rust-lang.org/cargo/reference/pkgid-spec.html

🌈 OPTIONS 🌈

💜 Package Selection

  • -p spec, --package spec — get the package ID for the given package instead of the current package. Like, "not this one, that one." 🎯

💖 Display Options

  • -v, --verbose — use verbose output. You can specify it twice for "very verbose" output, which includes extra output such as dependency warnings and build script output. May also be specified with the term.verbose config value (https://doc.rust-lang.org/cargo/reference/config.html).
  • -q, --quiet — do not print cargo log messages. May also be specified with the term.quiet config value (https://doc.rust-lang.org/cargo/reference/config.html).
  • --color when — control when colored output is used. Valid values:
    • auto (default): automatically detect if color support is available on the terminal. ✨
    • always: always display colors. 🌈
    • never: never display colors. 💀

May also be specified with the term.color config value (https://doc.rust-lang.org/cargo/reference/config.html).

🎀 Manifest Options

  • --manifest-path path — path to the Cargo.toml file. By default, Cargo searches for the Cargo.toml file in the current directory or any parent directory. It's like a little scavenger hunt, ngl. 🔍
  • --locked — asserts that the exact same dependencies and versions are used as when the existing Cargo.lock file was originally generated. Cargo will exit with an error when either of the following scenarios arises:
    • The lock file is missing.
    • Cargo attempted to change the lock file due to a different dependency resolution.

It may be used in environments where deterministic builds are desired, such as in CI pipelines. Determinism girlies, this one's for you. 👑

  • --offline — prevents Cargo from accessing the network for any reason. Without this flag, Cargo will stop with an error if it needs to access the network and the network is not available. With this flag, Cargo will attempt to proceed without the network if possible.
Beware that this may result in different dependency resolution than online mode. Cargo will restrict itself to crates that are downloaded locally, even if 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 going offline.

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

  • --frozen — equivalent to specifying both --locked and --offline. Two flags in a trench coat. 🧥
  • --lockfile-path PATH — changes the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing --lockfile-path will ignore the existing lockfile at the default path, and instead will either use the lockfile from PATH, or write a new lockfile into the provided PATH if it doesn't exist. This flag can be used to run most commands in read-only directories, writing lockfile into the provided PATH.
This option is only available on the nightly channel (https://doc.rust-lang.org/book/appendix-07-nightly-rust.html) and requires the -Z unstable-options flag to enable (see #14421 https://github.com/rust-lang/cargo/issues/14421).

🌸 Common Options

  • +toolchain — if Cargo has been installed with rustup, and the first argument to cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly). See the rustup documentation (https://rust-lang.github.io/rustup/overrides.html) for more information about how toolchain overrides work.
  • --config KEY=VALUE or PATH — overrides a Cargo configuration value. The argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. This flag may be specified multiple times. See the command-line overrides section (https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides) for more information.
  • -C PATH — changes the current working directory before executing any specified operations. This affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example. This option must appear before the command name, for example cargo -C path/to/my-project build.
This option is only available on the nightly channel (https://doc.rust-lang.org/book/appendix-07-nightly-rust.html) and requires the -Z unstable-options flag to enable (see #10098 https://github.com/rust-lang/cargo/issues/10098).
  • -h, --help — prints help information. 🫶
  • -Z flag — unstable (nightly-only) flags to Cargo. Run cargo -Z help for details.

🧚 ENVIRONMENT 🧚

See the reference (https://doc.rust-lang.org/cargo/reference/environment-variables.html) for details on environment variables that Cargo reads. Yes, it's a link. Go read it, bestie, I believe in you. 📖

⭐ EXIT STATUS ⭐

  • 0: Cargo succeeded. 🎉
  • 101: Cargo failed to complete. 😭

🔥 EXAMPLES 🔥

  1. Retrieve package specification for foo package:
cargo pkgid foo
  1. Retrieve package specification for version 1.0.0 of foo:
cargo pkgid foo@1.0.0
  1. Retrieve package specification for foo from crates.io:
cargo pkgid https://github.com/rust-lang/crates.io-index#foo
  1. Retrieve package specification for foo from a local package:
cargo pkgid file:///path/to/local/package#foo

🦋 SEE ALSO 🦋

cargo(1), cargo-generate-lockfile(1), cargo-metadata(1), Package ID Specifications (https://doc.rust-lang.org/cargo/reference/pkgid-spec.html), JSON messages (https://doc.rust-lang.org/cargo/reference/external-tools.html#json-messages)

and that's the whole page, bestie, we ate and left no crumbs 💅✨ this was CARGO-PKGID(1) from Cargo's General Commands Manual — go forth and print fully qualified package specs, you've got this 🫶💖🎀

📦 where this page comes from