OPAM-LIST(1)

📦
version 2.6.1 · 8 versions
, in arch rolling, fedora 44

💖 opam-list — the "who's even in the building" command 💖

okay bestie, welcome to OPAM-LIST(1) from the Opam Manual 🫶 this is the one you pull up when you wanna know what packages exist, what's installed, what's vibing in your switch, all of it.

✨ NAME ✨

opam-list — Display the list of available packages. that's it, that's the whole job, and she does it flawlessly 👑

🌸 SYNOPSIS 🌸

opam list [--check] [--no-depexts] [--silent] [OPTION]… [PATTERNS]…

🦋 DESCRIPTION 🦋

so like, this command lists selections of opam packages. super simple concept, extremely useful execution 💅

No arguments? She shows you the list of currently installed packages. With pattern arguments? She lists all available packages matching one of those patterns. iconique behaviour honestly ✨

Unless you pass the --short switch, the output format is one package per line, and every line has:

  • the name of the package
  • the installed version, or -- if the package isn't installed
  • a short description

and here's the cute detail — in color mode, manually installed packages (as opposed to the ones that got automatically installed because of dependencies) are underlined. the way she distinguishes her faves… we love to see it 😭💖

Peep the section PACKAGE SELECTION OPTIONS for all the ways to select which packages get displayed, and OUTPUT FORMAT OPTIONS to customise how the output looks.

For a more detailed description of packages, go see opam show. And for extended search capabilities within the packages' metadata, go see opam search. they're the extended universe besties 🎀

🎀 ARGUMENTS 🎀

  • PATTERNS — package patterns with globs. Unless --search is specified, they match against a NAME or NAME.VERSION 🧚

🔥 ORDER-SENSIBLE SELECTORS 🔥

okay this is the part where the order you type things in actually matters, no cap. These options are sensible to the order they are given to the command.

For example: --available --latests-only will first list all the available packages, then choose only the latest packages in that set. But --latests-only --available will first list all the latest packages, then only show the ones that are available in that set. same flags, different order, different result. it's giving pipeline energy 🌈

  • -a, --available — List only packages that are available on the current system
  • -A, --all — Include all, even uninstalled or unavailable packages. everyone's invited 🫶
  • --base — Removed in 2.1, use --invariant instead. she's retired bestie, don't try to hit her up 💀
  • -i, --installed — List installed packages only. This is the default when no further arguments are supplied
  • --installable — List only packages that can be installed on the current switch (this calls the solver and may be more costly; a package depending on an unavailable package may be available, but is never installable). pricey but thorough ✨
  • --invariant — List only the immutable base of the current switch (i.e. invariant packages)
  • --latests-only — List only the latest version of each package.
  • --pinned — List only the pinned packages 📌
  • --roots, --installed-roots — List only packages that were explicitly installed, excluding the ones installed as dependencies. the OGs, the ones you actually chose 🥹

👑 PACKAGE SELECTION OPTIONS 👑

these options will always be given to the command in the same order, regardless of the order you typed them in. no order-shenanigans down here, she's stable 💅

  • --coinstallable-with=PACKAGES — Only list packages that are compatible with all of PACKAGES. no drama, everybody gets along 🫶
  • --conflicts-with=PACKAGES — List packages that have declared conflicts with at least one of the given list. This includes conflicts defined from the packages in the list, from the other package, or by a common conflict-class: field. messy, but documented 💀
  • --depends-on=PACKAGES — List only packages that depend on one of (comma-separated) PACKAGES.
  • --depopts — Include optional dependencies in dependency requests.
  • --dev — Include development packages in dependencies.
  • --field-match=FIELD:PATTERN — Filter packages with a match for PATTERN on the given FIELD
  • --has-flag=FLAG — Only include packages which have the given flag set. Package flags are one of: light-uninstall verbose plugin compiler conf 🚩
  • --has-tag=TAG — Only includes packages which have the given tag set
  • --no-switch — List what is available from the repositories, without consideration for the current (or any other) switch (installed or pinned packages, etc.). switch? never heard of her 🙈
  • --nobuild — Exclude build dependencies (they are included by default).
  • --or — Instead of selecting packages that match all the criteria, select packages that match any of them. inclusivity mode ✨
  • --owns-file=FILE — Finds installed packages responsible for installing the given file 🕵️
  • --post — Include dependencies tagged as post.
  • --recursive — With --depends-on and --required-by, display all transitive dependencies rather than just direct dependencies. go deep or go home 🦋
  • --repos=REPOS — Include only packages that took their origin from one of the given repositories (unless no-switch is also specified, this excludes pinned packages).
  • --required-by=PACKAGES — List only the dependencies of (comma-separated) PACKAGES.
  • --resolve=PACKAGES — Restrict to a solution to install (comma-separated) PACKAGES, i.e. a consistent set of packages including those. This is subtly different from --required-by --recursive, which is more predictable and can't fail, but lists all dependencies independently without ensuring consistency. Without --installed, the answer is self-contained and independent of the current installation. With --installed, it's computed from the set of currently installed packages. --no-switch further makes the solution independent from the currently pinned packages, architecture, and compiler version. The combination with --depopts is not supported. 🚫 big brain option, read it twice fr fr
  • --search — Match PATTERNS against the full descriptions of packages, and require all of them to match, instead of requiring at least one to match against package names (unless --or is also specified).
  • -t, --with-test, --test — Include test-only dependencies.
  • --with-dev-setup — Include developer only dependencies.
  • --with-doc, --doc — Include doc-only dependencies. 📚

🌈 OUTPUT FORMAT OPTIONS 🌈

  • --columns=COLUMNS — Select the columns to display among: name, version, package, synopsis, synopsis-or-target, description, <field>:, installed-version, pin, source-hash, opam-file, all-installed-versions, available-versions, all-versions, repository, installed-files, vc-ref, depexts. The special form <field>: (field name followed by colon, e.g., license:) selects an arbitrary field. The default is name when --short is present and name, installed-version, synopsis-or-target otherwise. pick your own adventure bestie 💅
  • -e, --external, --depexts — Instead of displaying the packages, display their external dependencies that are associated with the current system. This excludes other display options. Rather than using this directly, you should probably head for the depext plugin, that will use your system package management system to handle the installation of the dependencies. Run opam depext. 👀
  • --normalise — Print the values of opam fields normalised
  • -S, --sort — Sort the packages in dependency order (i.e. an order in which they could be individually installed.) perfect lineup, no chaos ✨
  • -s, --short — Don't print a header, and sets the default columns to name only. If you need package versions included, use --columns=package instead
  • --separator=STRING (absent= ) — Set the column-separator string
  • -V, --all-versions — Normally, when multiple versions of a package match, only one is shown in the output (the installed one, the pinned-to one, or, failing that, the highest one available or the highest one). This flag disables this behaviour and shows all matching versions. This also changes the default display format to include package versions instead of just package names (including when --short is set). This is automatically turned on when a single non-pattern package name is provided on the command-line. show me EVERYONE 💖
  • --vars=[VAR=STR,...] — Define the given variable bindings. Typically useful with --external to override the values for arch, os, os-distribution, os-version, os-family.
  • --wrap — Wrap long lines, the default being to truncate when displaying on a terminal, or to keep as is otherwise

💜 OPTIONS 💜

  • --check — Don't write anything in the output, exit with return code 0 if the list is not empty, 1 otherwise. silent but opinionated, we stan 🎀
  • --no-depexts — Disable external dependencies handling for the query. This can be used to include packages that are marked as unavailable because of an unavailable system dependency.
  • --silent — Removed in 2.1, use --check instead. another retired queen, pls stop calling her 💀

✨ COMMON OPTIONS ✨

These are the universal settings, bestie — the ones that work across all the commands. No cap. 🫶

  • --best-effort — If opam can't install every single package you asked for, it doesn't just give up 😤: it tries to install as many as possible. But heads up: not every external solver supports this (recent versions of aspcud or mccs should). Equivalent to setting the $OPAMBESTEFFORT environment variable.
  • --cli=MAJOR.MINOR (absent=2.6) — Use the command-line interface syntax and semantics of MAJOR.MINOR. This is meant for anything persistent you do with opam — scripts, blog posts, etc. — so that any version of opam in the same MAJOR series behaves like the specified MINOR release. The flag was not available in opam 2.0, so if you want the 2.0 CLI, set the OPAMCLI environment variable to 2.0 instead of using this parameter.
  • --color=WHEN — Colorize the output. WHEN has to be one of always, never or auto. 🌈
  • --confirm-level=LEVEL — Set the confirmation level. LEVEL must be one of ask, no, yes or unsafe-yes. You can pass this more than once. If --yes or --no are also given, the value of the last --confirm-level is what counts. Equivalent to setting $OPAMCONFIRMLEVEL.
  • --criteria=CRITERIA — Specify your preferences for dependency solving, just for this run. It overrides $OPAMCRITERIA, $OPAMFIXUPCRITERIA and $OPAMUPGRADECRITERIA. For the details on the supported language and the external solvers available, see http://opam.ocaml.org/doc/External_solvers.html. A general guide to using solver preferences lives at http://www.dicosmo.org/Articles/usercriteria.pdf. 📚
  • --cudf=FILENAME — Debug option: save the CUDF requests sent to the solver to FILENAME-<n>.cudf, where <n> is the n-th call to the solver during the opam run. 🛠️
  • --debug — Print debug message to stderr. Equivalent to setting $OPAMDEBUG to "true". 🐛
  • --debug-level=LEVEL — Like --debug, but you get to specify the debug level (--debug sets it to 1). Equivalent to setting $OPAMDEBUG to a positive integer.
  • --git-version — Print the git version of opam, if set (i.e. you are using a development version), and exit. 👑
  • --help[=FMT] (default=auto) — Show this help in format FMT. The value FMT must be one of auto, pager, groff or plain. With auto, the format is pager or plain whenever the TERM env var is dumb or undefined. 💖
  • --ignore-pin-depends — Ignore extra pins required by packages that get pinned, whether that happens manually through opam pin or through opam install DIR. Equivalent to setting IGNOREPINDEPENDS=true.
  • --json=FILENAME — Save the results of the opam run in a computer-readable file. If the filename contains the character %, it gets replaced by an index that doesn't overwrite an existing file. Similar to setting the $OPAMJSON variable. ✨
  • --no — Answer no to all opam yes/no questions without prompting. See also --confirm-level. Equivalent to setting $OPAMNO to "true".
  • --no-aspcud — Removed in 2.1. 💀
  • --no-auto-upgrade — When configuring or updating a repository that was written for an earlier opam version (1.2), opam internally converts it to the current format. This disables that behaviour. Note that repositories should define their format version in a 'repo' file at their root, or they'll be assumed to be in the older format. It's preferable, in any case, to upgrade repositories manually using opam admin upgrade [--mirror URL] when possible. 🧚
  • --no-self-upgrade — Opam will replace itself with a newer binary found at OPAMROOT/opam if present. This disables that behaviour.
  • -q, --quiet — Disables --verbose. 🤫
  • --root=ROOT — Use ROOT as the current root path. Equivalent to setting $OPAMROOT to ROOT.
  • --safe, --readonly — Make sure nothing will be automatically updated or rewritten. Useful for calling from completion scripts, for example. It will fail whenever such an operation is needed; it also avoids waiting for locks, skips interactive questions and overrides the $OPAMDEBUG variable. Equivalent to setting the environment variable $OPAMSAFE. 🛡️
  • --solver=CMD — Specify the CUDF solver to use for resolving package installation problems. This is either a predefined solver — this version of opam supports builtin-mccs+lp(), builtin-mccs+glpk, builtin-dummy-z3-solver, builtin-0install, aspcud, mccs, aspcud-old, packup — or a custom command that should contain the variables %{input}%, %{output}%, %{criteria}%, and optionally %{timeout}%. Equivalent to setting $OPAMEXTERNALSOLVER. 🔥
  • --strict — Fail whenever an error is found in a package definition or a configuration file. The default is to continue silently if possible. 🚨
  • --switch=SWITCH — Use SWITCH as the current compiler switch. Equivalent to setting $OPAMSWITCH to SWITCH.
  • --use-internal-solver — Disable any external solver and use the built-in one. (This requires that opam has been compiled with a built-in solver.) Equivalent to setting $OPAMNOASPCUD or $OPAMUSEINTERNALSOLVER.
  • -v, --verbose — Be more verbose. One -v shows all package commands; repeat it to also display commands called internally (e.g. tar, curl, patch etc.). Repeating n times is equivalent to setting $OPAMVERBOSE to "n". 📣
  • --version — Show version information.
  • -w, --working-dir — Whenever updating packages that are bound to a local, version-controlled directory, update to the current working state of their source instead of the last committed state, or the ref they're pointing to. Since the source directory is copied as it is, if it isn't clean it may result in an opam build failure. This only affects packages explicitly listed on the command-line. It can also be set with $OPAMWORKINGDIR. 🛠️
  • -y, --yes — Answer yes to all opam yes/no questions without prompting. See also --confirm-level. Equivalent to setting $OPAMYES to "true".

💖 THE ENVIRONMENT VARIABLES 💖

okok so opam reads a whole list of environment variables, bestie. And here's the rules for the boolean ones: set them to "0", "no", "false" or the empty string to disable them, and "1", "yes" or "true" to enable them. That's it, that's the whole vibe. 🫶

  • OPAMALLPARENS — surround all filters with parenthesis.
  • OPAMASSUMEDEPEXTS — see option --assume-depexts.
  • OPAMAUTOANSWER — internal use only. (no thoughts, head empty, don't touch 💅)
  • OPAMAUTOREMOVE — see remove option --auto-remove.
  • OPAMBESTEFFORT — see option --best-effort.
  • OPAMBESTEFFORTPREFIXCRITERIA — sets the string that must be prepended to the criteria when the --best-effort option is set, and is expected to maximise the opam-query property in the solution.
  • OPAMBUILDDOC — removed in 2.1. ⚰️ rest in peace queen
  • OPAMBUILDTEST — removed in 2.1. ⚰️
  • OPAMCLI — see option --cli.
  • OPAMCOLOR — when set to always or never, sets a default value for the --color option.
  • OPAMCONFIRMLEVEL — see option --confirm-level. OPAMCONFIRMLEVEL has priority over OPAMYES and OPAMNO.
  • OPAMCRITERIA — specifies user preferences for dependency solving. The default value depends on the solver version, use config report to know the current setting. See also option --criteria.
  • OPAMCUDFFILE — save the cudf graph to file-actions-explicit.dot.
  • OPAMCUDFTRIM — controls the filtering of unrelated packages during CUDF preprocessing.
  • OPAMCURL — can be used to select a given curl program. See OPAMFETCH for more options.
  • OPAMDEBUG — see options --debug and --debug-level.
  • OPAMDEBUGSECTIONS — if set, limits debug messages to the space-separated list of sections. Sections can optionally have a specific debug level (for example, CLIENT:2 or CLIENT CUDF:2), but otherwise use --debug-level.
  • OPAMDIGDEPTH — defines how aggressive the lookup for conflicts during CUDF preprocessing is.
  • OPAMDOWNLOADJOBS — sets the maximum number of simultaneous downloads.
  • OPAMDROPWORKINGDIR — overrides packages previously updated with --working-dir on update. Without this variable set, opam would keep them unchanged unless explicitly named on the command-line.
  • OPAMDRYRUN — see option --dry-run.
  • OPAMEDITOR — sets the editor to use for opam file editing, overrides $EDITOR and $VISUAL.
  • OPAMERRLOGLEN — sets the number of log lines printed when a sub-process fails. 0 to print all.
  • OPAMEXTERNALSOLVER — see option --solver.
  • OPAMFAKE — see option --fake.
  • OPAMFETCH — specifies how to download files: either wget, curl or a custom command where variables %{url}%, %{out}%, %{retry}%, %{compress}% and %{checksum}% will be replaced. Overrides the download-command value from the main config file.
  • OPAMFIXUPCRITERIA — same as OPAMUPGRADECRITERIA, but specific to fixup and reinstall.
  • OPAMIGNOREAVAILABLE — see install option --ignore-available-on.
  • OPAMIGNORECONSTRAINTS — see install option --ignore-constraints-on.
  • OPAMIGNOREPINDEPENDS — see option --ignore-pin-depends.
  • OPAMINPLACEBUILD — see option --inplace-build.
  • OPAMJOBS — sets the maximum number of parallel workers to run.
  • OPAMJSON — log json output to the given file (use character % to index the files).
  • OPAMKEEPBUILDDIR — see install option --keep-build-dir.
  • OPAMKEEPLOGS — tells opam to not remove some temporary command logs and some backups. This skips some finalisers and may also help to get more reliable backtraces.
  • OPAMLOCKED — combination of --locked and --lock-suffix options.
  • OPAMLOGS — logdir sets log directory, default is a temporary directory in /tmp.
  • OPAMMAKECMD — set the system make command to use.
  • OPAMMERGEOUT — merge process outputs, stderr on stdout.
  • OPAMNO — answer no to any question asked, see options --no and --confirm-level. OPAMNO is ignored if either OPAMCONFIRMLEVEL or OPAMYES is set.
  • OPAMNOAGGREGATE — with opam admin check, don't aggregate packages.
  • OPAMNOASPCUD — deprecated. 🙈
  • OPAMNOAUTOUPGRADE — disables automatic internal upgrade of repositories in an earlier format to the current one, on update or init.
  • OPAMNOCHECKSUMS — enables option --no-checksums when available.
  • OPAMNODEPEXTS — disables system dependencies handling, see option --no-depexts.
  • OPAMNOENVNOTICE — internal.
  • OPAMNOSELFUPGRADE — see option --no-self-upgrade.
  • OPAMPINKINDAUTO — sets whether version control systems should be detected when pinning to a local path. Enabled by default since 1.3.0.
  • OPAMPRECISETRACKING — fine grain tracking of directories.
  • OPAMPREPRO — set this to false to disable CUDF preprocessing. Less efficient, but might help debugging solver issue.
  • OPAMREPOSITORYTARRING — internally store all non-vcs repositories as tar.gz files (by default, http repositories are stored as archive). This can be much faster on filesystems that don't cope well with scanning large trees. All operation are done in-memory, no I/O for scanning the repository.
  • OPAMREQUIRECHECKSUMS — enables option --require-checksums when available (e.g. for opam install).
  • OPAMRETRIES — sets the number of tries before failing downloads.
  • OPAMREUSEBUILDDIR — see option --reuse-build-dir.
  • OPAMROOT — see option --root. This is automatically set by opam env --root=DIR --set-root.
  • OPAMROOTISOK — don't complain when running as root.
  • OPAMSAFE — see option --safe.
  • OPAMSHOW — see option --show.
  • OPAMSKIPUPDATE — see option --skip-updates.
  • OPAMSKIPVERSIONCHECKS — bypasses some version checks. Unsafe, for compatibility testing only.
  • OPAMSOLVERALLOWSUBOPTIMAL — (default true) allows some solvers to still return a solution when they reach timeout; while the solution remains assured to be consistent, there is no guarantee in this case that it fits the expected optimisation criteria. If true, opam will continue with a warning, if false a timeout is an error. Currently only the builtin-z3 backend handles this degraded case.
  • OPAMSOLVERTIMEOUT — change the time allowance of the solver. Default is 60.0, set to 0 for unlimited. Note that all solvers may not support this option.
  • OPAMSOLVERTOLERANCE — changes the tolerance towards the solver choosing an unoptimized solution (i.e. might pull outdated packages). Typical values range from 0.0 (best solution known to the solver) to 1.0 (unoptimized solution). Default is 0.0. This option is useful in case the solver can't find a solution in a reasonable time (see $OPAMSOLVERTIMEOUT). Note that all solvers may not support this option.
  • OPAMSTATS — removed in 2.4. ⚰️💀
  • OPAMSTATUSLINE — display a dynamic status line showing what's currently going on on the terminal. (one of always, never or auto)
  • OPAMSTRICT — fail on inconsistencies (file reading, switch import, etc.).
  • OPAMSWITCH — see option --switch. Automatically set by opam env --switch=SWITCH --set-switch.
  • OPAMUNLOCKBASE — see install option --unlock-base.
  • OPAMUPGRADECRITERIA — specifies user preferences for dependency solving when performing an upgrade. Overrides OPAMCRITERIA in upgrades if both are set. See also option --criteria.
  • OPAMUSEINTERNALSOLVER — see option --use-internal-solver.
  • OPAMUSEOPENSSL — removed in 2.2. ⚰️
  • OPAMUTF8 — use UTF8 characters in output (one of always, never or auto). By default auto, which is determined from the locale.
  • OPAMUTF8MSGS — use extended UTF8 characters (camels 🐪) in opam messages. Implies OPAMUTF8. This is set by default on macOS only.
  • OPAMVALIDATIONHOOK — if set, uses the %{hook}% command to validate an opam repository update.
  • OPAMVERBOSE — see option --verbose.
  • OPAMVERBOSEON — see option --verbose-on.
  • OPAMVERSIONLAGPOWER — do not use. 🚫 bestie I'm begging you
  • OPAMWITHDEVSETUP — see install option --with-dev-setup.
  • OPAMWITHDOC — see install option --with-doc.
  • OPAMWITHTEST — see install option --with-test.
  • OPAMWORKINGDIR — see option --working-dir.
  • OPAMYES — see options --yes and --confirm-level. OPAMYES has priority over OPAMNO and is ignored if OPAMCONFIRMLEVEL is set.
  • OPAMVAR_var — overrides the contents of the variable var when substituting %{var}% strings in opam files.
  • OPAMVAR_package_var — overrides the contents of the variable package:var when substituting %{package:var}% strings in opam files.

🌈 CLI VERSION 🌈

okay this part is literally the most responsible-girlboss section of the whole page, listen up 📣

All scripts and programmatic invocations of opam should use --cli in order to ensure that they work seamlessly with future versions of the opam client. Additionally, blog posts or other documentation can benefit, as it prevents information from becoming stale. like, future-proofing? we love to see it. ✨

Although opam only supports roots (~/.opam/) for the current version, it does provide backwards compatibility for its command-line interface.

Since CLI version support was only added in opam 2.1, use OPAMCLI to select 2.0 support (as opam 2.0 will just ignore it), and --cli=2.1 for 2.1 (or later) versions, since an environment variable controlling the parsing of syntax is brittle. To this end, opam displays a warning if OPAMCLI specifies a valid version other than 2.0, and also if --cli=2.0 is specified.

The command-line version is selected by using the --cli option or the OPAMCLI environment variable. --cli may be specified more than once, where the last instance takes precedence. OPAMCLI is only inspected if --cli is not given.

🫶 tl;dr for the besties: pass --cli, or set OPAMCLI, and last flag wins. opam will side-eye you with a warning in a couple of edge cases, but it's not mad, just disappointed. 😭

✨ EXIT STATUS ✨

Okay bestie, listen up, this is the part where opam tells you exactly what it's feeling via numbers. 💅

Exception alert!! The exec command is the rebel here: it returns 127 if the command wasn't found or couldn't be executed, and otherwise it just returns the command's own exit value. Everyone else plays by the rules below. 🙈
  • 0 — Slay! Success, or true for boolean queries. 🎀
  • 1 — False. This one shows up when a boolean return value is expected, like when you're running with --check, or for queries like opam lint.
  • 2 — Bad command-line arguments, OR command-line arguments pointing at an invalid context (think: a file that doesn't follow the expected format). Not it. 😭
  • 5 — Not found. You asked for something — a package, a version, a repository, etc. — that couldn't be found. She's just not there, bestie. 🦋
  • 10 — Aborted. The operation needed confirmation and you didn't give it. No consent, no operation. ✋
  • 15 — Could not acquire the locks required for the operation. The locks were locked. 🔒
  • 20 — There is no solution to the user request. This can be caused by asking to install two incompatible packages, for example. Math said no. 💀
  • 30 — Error in package definition, or other metadata files. Using --strict raises this error more often. 👀
  • 31 — Package script error. Some package operations were unsuccessful. This may be an error in the packages or an incompatibility with your system. This can be a partial error.
  • 40 — Sync error. Could not fetch some remotes from the network. This can be a partial error too. The wifi ghosted us. 🌐
  • 50 — Configuration error. Opam or system configuration doesn't allow the operation, and it needs fixing. The vibe is off and it's fixable. 🧚
  • 60 — Solver failure. The solver failed to return a sound answer. It can be due to a broken external solver, or an error in solver configuration. 🫠
  • 99 — Internal error. Something went wrong, likely due to a bug in opam itself. Blame the software, not yourself. 💖
  • 130 — User interrupt. SIGINT was received, generally due to the user pressing Ctrl+C.
  • 0 — on success.
  • 123 — on indiscriminate errors reported on standard error.
  • 124 — on command line parsing errors.
  • 125 — on unexpected internal errors (bugs).

📚 FURTHER DOCUMENTATION 📚

See https://opam.ocaml.org/doc. That's the spot for the deep lore, iykyk. 🌈

👑 AUTHORS 👑

Look at this absolute roster of main characters who built the thing you're using right now. Respect the legends:

  • David Allsopp <david@tarides.com>
  • Vincent Bernardoff <vb@luminar.eu.org>
  • Raja Boujbel <raja.boujbel@ocamlpro.com>
  • Kate Deplaix <kit-ty-kate@exn.st>
  • Roberto Di Cosmo <roberto@dicosmo.org>
  • Thomas Gazagnaire <thomas@gazagnaire.org>
  • Louis Gesbert <louis.gesbert@ocamlpro.com>
  • Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
  • Anil Madhavapeddy <anil@recoil.org>
  • Guillem Rieu <guillem.rieu@ocamlpro.com>
  • Ralf Treinen <ralf.treinen@pps.jussieu.fr>
  • Frederic Tuong <tuong@users.gforge.inria.fr>

🔍 SEE ALSO 🔍

  • opam(1) — yeah, the whole family tree starts there. 🫶

🐛 BUGS 🐛

Found something cursed? Check bug reports at https://github.com/ocaml/opam/issues. Reporting is a love language, fr fr. 💜

And that's the whole page, bestie — this little manual is from Opam 2.6.1 and it's dated OPAM-LIST(1). Go forth and list your packages with confidence. You ate. No cap. 💅✨🌸

📦 where this page comes from