MAMBA(1)

πŸ“¦
version 2.9.0 Β· 3 versions
, in epel 10

πŸ¦‹ MAMBA(1) β€” the manual page for mamba, but make it a group chat

okay so bestie. this is the manual page for mamba, and honestly? it's giving "your fave package manager finally learned to text back." πŸ’… the manual name is right up there in the title, so consider yourself formally introduced β€” now let's get into it.


✨ NAME ✨

mamba β€” literally the manual page for mamba 2.9.0. no cap, that's the whole name section. short, sweet, iconic. πŸŽ€


🌸 DESCRIPTION 🌸

Version: 2.9.0 β€” that's the one, bestie. remember it, write it down, tattoo it on your forearm, whatever works. πŸ’–

the invocation vibe is this, exactly as written:

redhat-linux-build/micromamba/mamba [OPTIONS] [SUBCOMMAND]

so like β€” options, then a subcommand. or options, then another option. it's flexible. it's main character energy. πŸ¦‹

🌈 OPTIONS:

  • -h, --help β€” prints this help message and then dips out. exit stage left. bye. πŸ‘‹
  • --version β€” that's it. that's the whole entry. no description given. mysterious. enigmatic. we love a lowkey icon. ✨

🧚 Configuration options:

  • --rc-file FILE1 FILE2... β€” paths to the configuration files to use. yes, plural, you can feed it a whole little stack of them, <italic>FILE1 FILE2...</italic> and all. πŸ“
  • --no-rc β€” disables the use of configuration files entirely. no config files, no problems, we're going rogue. πŸ™ˆ
  • --no-env β€” disables the use of environment variables. same chaotic energy, different source. πŸ’€

πŸ‘‘ Global options:

  • -v, --verbose β€” sets verbosity. and the way that more -v means more verbosity?? so -vvv is a thing you can literally type. go off. πŸ”₯
  • --log-level β€” sets the log level. the value is an enum, and it looks like this: ENUM:value in {critical->5,debug->1,error->4,info->2,off->6,trace->0,warning->3} OR {5,1,4,2,6,0,3}. so you can pass the name or the number, either slaps. πŸ’œ
  • -q, --quiet β€” sets quiet mode, meaning it prints less output. and heads up, bestie: it implicitly bypasses prompts as if --yes was used. sneaky but efficient. 🀫
  • -y, --yes β€” automatically answers yes on prompted questions. no more staring at a [y/N] prompt like it's a pop quiz. 😌
  • --json β€” reports all output as json. and β€” important β€” it implicitly bypasses prompts as if --yes was used. same auto-yes behavior, json flavored. 🫢
  • --offline β€” forces the use of cached repodata. airplane mode but make it package management. ✈️
  • --dry-run β€” only displays what would have been done. a little rehearsal, a little dress rehearsal, no actual commitment. 🎭
  • --download-only β€” only downloads and extracts packages, and does not link them into the environment. so you get the goods but they stay in the box. πŸ“¦
  • --use-uv β€” whether to use uv for installing pip dependencies. defaults to false. ngl, off by default, but the option is right there if you want it. ⭐

πŸŽ€ Prefix options:

  • -r, --root-prefix PATH β€” path to the root prefix, where PATH is the path, because obviously. 🌸
  • -p, --prefix PATH β€” path to the target prefix. this is the one you'll be reaching for a lot. 🫢
  • --relocate-prefix PATH β€” path to the relocation prefix. relocation, as in moving, as in we're shifting the whole vibe. πŸ¦‹
  • -n, --name NAME β€” name of the target prefix. a name! for your prefix! adorable. πŸ’–

πŸ’… SUBCOMMANDS:

  • shell β€” generate shell init scripts
  • create β€” create new environment
  • install β€” install packages in active environment
  • update β€” update packages in active environment
  • repoquery β€” find and analyze packages in active environment or channels
  • remove, uninstall β€” remove packages from active environment. two names, one job, both slay.
  • list β€” list packages in active environment
  • package β€” extract a package or bundle files into an archive
  • clean β€” clean package cache
  • config β€” configuration of micromamba
  • info β€” information about micromamba
  • constructor β€” commands to support using micromamba in constructor
  • env β€” see mamba/micromamba env --help. that's the whole description. go read that one, bestie. πŸ“–
  • activate β€” activate an environment
  • deactivate β€” deactivate the active environment
  • run β€” run an executable in an environment
  • ps β€” show, inspect or kill running processes. show! inspect! kill! pick your fighter. πŸ’€
  • auth β€” login or logout of a given host
  • search β€” find packages in active environment or channels. and yes, this is equivalent to the repoquery search command β€” they're literally the same thing, so use whichever one your heart says. πŸ’œ

⭐ SEE ALSO ⭐

the full documentation for mamba is maintained as a Texinfo manual. so if the info and mamba programs are properly installed at your site β€” properly, bestie, we're checking β€” then this command:

info mamba

should give you access to the complete manual. that's the whole treasure map. πŸ—ΊοΈβœ¨


and that's the page!! πŸŽ‰ mamba version 2.9.0, dated October 2026, manual page MAMBA(1) β€” thanks for reading, bestie, go forth and manage those packages, you're gonna ate πŸ’…πŸ«ΆπŸŒˆ

πŸ“¦ where this page comes from