OPAM-UNPIN(1)

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

💅 OPAM-UNPIN — bestie's guide to unpinning stuff 💅

Heyyy so welcome to OPAM-UNPIN, part of the Opam Manual fam. This one is literally an alias — it's not even doing its own thing, it's just pin remove in a cute little trench coat. Let's get into it 💖

✨ NAME ✨

opam-unpin — it's giving "an alias for pin remove." That's it, that's the whole job 🎀

✨ SYNOPSIS ✨

opam unpin [OPTION]… [ARG]…

✨ DESCRIPTION ✨

Okay so real talk: opam unpin is an alias for opam pin remove. Same energy, different name 🌸

And if you wanna know the details? Run opam pin --help and it'll spill everything. iykyk 💅

✨ PACKAGE BUILD OPTIONS ✨

These are all the build-time knobs and dials, bestie. Buckle up 🦋

  • --assume-depexts — Skips the install step for any system packages you're missing, and just tries to compile the opam packages anyway. If the install happens to work out, opam won't nag you about those system packages again. Heads up though: this only actually means anything if external dependency handling is turned on.
  • -b, --keep-build-dir — Keeps the build directories around after compiling packages. Exactly the same as setting $OPAMKEEPBUILDDIR to "true" ✨
  • --build-doc — Nope, removed in 2.1. Use --with-doc instead 💀
  • --build-test — Also removed in 2.1. Use --with-test instead 💀
  • -d, --with-doc — Builds the package documentation. Only affects packages you listed on the command-line, no sneaky extras. Same as setting $OPAMWITHDOC (or the deprecated $OPAMBUILDDOC) to "true" 🌈
  • --dry-run — Simulates the command but doesn't actually change anything. You can also flip this on with the $OPAMDEBUG environment variable 👑
  • --fake — Registers the actions into the opam database without actually performing them.
⚠️ WARNING: this option is dangerous and likely to break your opam environment. You probably want --dry-run. You've been warned. Fr fr, don't do it 🙈
  • --ignore-available-on[=PACKAGES] (default=) — Forces opam to mark the listed packages as available. Great for testing compatibility, but expect builds to break when you use it. Note that version constraints of the packages' dependencies are unaffected 💅
  • --ignore-constraints-on[=PACKAGES] (default=) — Forces opam to ignore version constraints on all dependencies of the listed packages. Again, cool for compatibility testing, but expect builds to break. Note that availability of the packages, version constraints on optional dependencies, and conflicts are all unaffected. Same as setting $OPAMIGNORECONSTRAINTS 🎀
  • --inplace-build — When compiling a package whose source is bound to a local directory, it processes the build and install actions right there in that directory instead of in a clean copy that opam manages. Only affects packages explicitly listed on the command-line. Same as setting $OPAMINPLACEBUILD to "true" 🌸
  • -j JOBS, --jobs=JOBS — Sets the max number of concurrent jobs to use. The default gets calculated from the number of cores you've got. You can also set it with the $OPAMJOBS environment variable ✨
  • --lock-suffix=SUFFIX (absent=locked) — Sets the locked files suffix to SUFFIX 💜
  • --locked — In commands that use opam files found from pinned sources, if a variant of the file with an added .locked extension exists (like foo.opam.locked sitting next to foo.opam), that one gets used instead. This is typically useful for offering a more specific set of dependencies and reproducing similar build contexts — hence the name, bestie. The lock option can generate files like that, based on the versions of the dependencies currently installed on your host. Same as setting the $OPAMLOCKED environment variable. Note that this option doesn't generally affect already pinned packages 👑
  • -m MAKE, --make=MAKE — Removed in 2.1. Use opam config set[-global] make MAKE instead 💀
  • --no-checksums — Doesn't verify the checksum of downloaded archives. Same as setting $OPAMNOCHECKSUMS to "true" 🦋
  • --no-depexts — Temporarily disables handling of external dependencies. Use this if a package isn't available on your system package manager but you installed the required dependency by hand. Implies --assume-depexts, and stores the exceptions upon success as well 🎀
  • --require-checksums — Rejects installation of packages that don't provide a checksum for the upstream archives. Same as setting $OPAMREQUIRECHECKSUMS to "true" 🔥
  • --reuse-build-dir — Reuses existing build directories (the ones you kept with --keep-build-dir) instead of compiling from a fresh clone of the source. Can be faster, but also can lead to failures if the build systems of the packages don't handle upgrades of dependencies well. Same as setting $OPAMREUSEBUILDDIR to "true" 😭
  • --show-actions — Calls the solver and displays the actions. Doesn't perform any changes. Same as setting $OPAMSHOW ✨
  • --skip-updates — When you run an install, upgrade or reinstall on source-pinned packages, they normally get updated from their origin first. This flag disables that behaviour and keeps them at their version in cache. Same as setting $OPAMSKIPUPDATE 💖
  • -t, --with-test — Builds and runs the package unit-tests. Only affects packages listed on the command-line. Same as setting $OPAMWITHTEST (or the deprecated $OPAMBUILDTEST) to "true" 🌈
  • --unlock-base — Removed in 2.1. Use --update-invariant instead 💀
  • --update-invariant — Allows changes to the packages set as switch base (typically, the main compiler). Use with caution! Same as setting the $OPAMUNLOCKBASE environment variable ⭐
  • --verbose-on=PACKAGES — Gets more verbose on specific packages. Same as setting $OPAMVERBOSE 👑
  • --with-dev-setup — Includes development tools only dependencies 🧚

✨ OPTIONS ✨

The main-character options, let's gooo 🫶

  • --all — When unpinning, removes all pins in the given switch 💅
  • --current — When pinning, uses the currently installed version and metadata of the package: this avoids reinstallations caused by upstream metadata changes, and can also be used to keep a package that was removed upstream 👑
  • --dev-repo — Pins to the upstream package source for the latest development version 🔥
  • -e, --edit — With opam pin add, edits the opam file as with opam pin edit after pinning ✨
  • -k KIND, --kind=KIND — Sets the kind of pinning. Must be one of version, path, http, git, darcs, hg, none or auto. If it's unset or auto, it gets inferred from the format of the target — defaulting to the appropriate version control if one is detected in the given directory, or to path otherwise. OPAMPINKINDAUTO can be set to "0" to disable automatic detection of version control. Use none to pin without a target (for virtual packages) 🌸
  • -n, --no-action — Just records the new pinning status, and doesn't prompt for (re)installation or removal of affected packages 🎀
  • --normalise — Prints a list of available packages to pin in the format name.version^url, which is comprehensible by opam pin add. Available only with the scan subcommand. An example of use is opam pin scan . --normalise | grep foo | xargs opam pin add 💜
  • --recursive — Allows recursive lookups of *.opam files. Cf. --subpath also 🦋
  • -s, --short — Outputs raw lists of names, one per line, skipping any details 😌
  • --subpath=PATH — *.opam files get retrieved from the given sub directory instead of the top directory. Sources are then taken from the targeted sub directory — internally only this subdirectory is copied/fetched. Can be combined with --recursive to get a recursive lookup on the subpath 🌈
  • --with-version=VERSION — Sets the pinning version to VERSION for named PACKAGES or packages retrieved from TARGET. It has priority over any other version specification (opam file version field, name.vers argument). When pinning to a version, the package source from that version is used, but declared as being VERSION to opam. Using --with-version is equivalent to using --edit and adjusting the version in the package definition file ⭐

more coming bestie, don't go anywhere 💖

✨ COMMON OPTIONS ✨

okay bestie, these flags? they work on literally every single opam command. like, the whole squad. let's go 💅

  • --best-effort — don't crash out just because opam couldn't install everything you asked for; it'll try to install as many as it possibly can. heads up tho: not every external solver plays nice with this option (recent versions of aspcud or mccs should be fine 🫶). it's the same as setting the $OPAMBESTEFFORT environment variable.
  • --cli=MAJOR.MINOR (absent=2.6) — makes opam use the command-line interface syntax and semantics of MAJOR.MINOR. this is for anyone doing persistent opam stuff — scripts, blog posts, all that — where any opam version in the same MAJOR series will behave exactly like the MINOR release you picked. important lore: this flag didn't exist in opam 2.0, so if you want the 2.0 CLI, you gotta set the OPAMCLI environment variable to 2.0 instead of using this parameter. iykyk 😭
  • --color=WHEN — colorizes the output, obviously 💖. WHEN has to be one of always, never or auto.
  • --confirm-level=LEVEL — sets the confirmation level. LEVEL must be one of ask, no, yes or unsafe-yes. you can pass it more than once! and if --yes or --no are also hanging around, the value of the last --confirm-level is the one that counts. this is equivalent to setting $OPAMCONFIRMLEVEL.
  • --criteria=CRITERIA — tells opam your user preferences for dependency solving, just for this run. it overrides $OPAMCRITERIA, $OPAMFIXUPCRITERIA and $OPAMUPGRADECRITERIA. for the deets on the supported language and which external solvers exist, look at http://opam.ocaml.org/doc/External_solvers.html. and there's a whole general guide to using solver preferences at http://www.dicosmo.org/Articles/usercriteria.pdf 📚.
  • --cudf=FILENAME — debug option bestie 🐛: it saves the CUDF requests sent to the solver into FILENAME-<n>.cudf, where <n> is the n-th call to the solver during the opam run.
  • --debug — prints debug messages to stderr. equivalent to setting $OPAMDEBUG to "true".
  • --debug-level=LEVEL — same energy as --debug, but you get to pick the debug level (--debug just sets it to 1). equivalent to setting $OPAMDEBUG to a positive integer.
  • --git-version — prints the git version of opam, if it's set (aka you're running a development version), then exits. like a little peek behind the curtain 🦋.
  • --help[=FMT] (default=auto) — shows this very help in format FMT. FMT must be one of auto, pager, groff or plain. with auto, the format becomes pager or plain whenever the TERM env var is dumb or undefined.
  • --ignore-pin-depends — ignores the extra pins that pinned packages require — whether they got pinned manually via opam pin or through opam install DIR. this is equivalent to setting IGNOREPINDEPENDS=true.
  • --json=FILENAME — saves the results of the opam run into 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 — answers no to every opam yes/no question without ever prompting you. see also --confirm-level. this is equivalent to setting $OPAMNO to "true".
  • --no-aspcud — removed in 2.1. gone. ghosted. 💀
  • --no-auto-upgrade — so when opam configures or updates a repository written for an earlier opam version (1.2), it internally converts it to the current format. this flag disables that behaviour. note that repositories should define their format version in a 'repo' file at their root, otherwise they'll be assumed to be in the older format. and honestly? it's preferable in any case to upgrade the repositories manually with opam admin upgrade [--mirror URL] when you can 🌸.
  • --no-self-upgrade — normally opam will replace itself with a newer binary found at OPAMROOT/opam if one's there 👀. this disables that behaviour.
  • -q, --quiet — disables --verbose.
  • --root=ROOT — uses ROOT as the current root path. equivalent to setting $OPAMROOT to ROOT.
  • --safe, --readonly — makes sure nothing gets automatically updated or rewritten. super useful for calling from completion scripts, for example. it'll 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 — picks the CUDF solver used 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 containing the variables %{input}%, %{output}%, %{criteria}%, and optionally %{timeout}%. equivalent to setting $OPAMEXTERNALSOLVER.
  • --strict — fails whenever an error turns up in a package definition or a configuration file. the default is to keep going silently if possible 🤫.
  • --switch=SWITCH — uses SWITCH as the current compiler switch. equivalent to setting $OPAMSWITCH to SWITCH.
  • --use-internal-solver — disables any external solver and uses the built-in one instead (this requires that opam was 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 (like tar, curl, patch, etc.). repeating it n times is equivalent to setting $OPAMVERBOSE to "n".
  • --version — shows version information.
  • -w, --working-dir — whenever opam updates packages that are bound to a local, version-controlled directory, this updates 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 gets 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. can also be set with $OPAMWORKINGDIR.
  • -y, --yes — answers yes to all opam yes/no questions without prompting. see also --confirm-level. equivalent to setting $OPAMYES to "true" 💖

🌸 ENVIRONMENT 🌸

okay bestie, this is the part where opam reads your ~vibes~ from the environment 💅 opam makes use of the environment variables listed here, and yes, naming is all-caps-and-no-underscores, that's just the brand.

quick rules for the boolean girlies: set it to 0, no, false, or the empty string to disable it, and 1, yes or true to enable it. that's it, that's the whole vibe check ✅

  • OPAMALLPARENS — surround all filters with parenthesis.
  • OPAMASSUMEDEPEXTS — see the option --assume-depexts.
  • OPAMAUTOANSWER — internal use only. not for us, bestie 🙈
  • OPAMAUTOREMOVE — see the remove option --auto-remove.
  • OPAMBESTEFFORT — see the option --best-effort.
  • OPAMBESTEFFORTPREFIXCRITERIA — sets the string that must be prepended to the criteria when the --best-effort option is set, and it's expected to maximise the opam-query property in the solution.
  • OPAMBUILDDOC — removed in 2.1. she's gone, we don't talk about her 💀
  • OPAMBUILDTEST — removed in 2.1.
  • OPAMCLI — see the option `--cli'.
  • OPAMCOLOR — when set to always or never, sets a default value for the --color option.
  • OPAMCONFIRMLEVEL — see the option --confirm-level. heads up: OPAMCONFIRMLEVEL has priority over OPAMYES and OPAMNO. she's the main character here 👑
  • OPAMCRITERIA — specifies user preferences for dependency solving. the default value depends on the solver version, so 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, and it overrides $EDITOR and $VISUAL. she overrules everyone, periodt.
  • 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 the install option --ignore-available-on.
  • OPAMIGNORECONSTRAINTS — see the 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. sad for her but rules are rules ✋
  • OPAMNOAGGREGATE — with opam admin check, don't aggregate packages.
  • OPAMNOASPCUD — Deprecated. we said what we said 🫠
  • 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. lowkey genius ngl ✨
  • 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. bestie please, only for science 🧪
  • 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 willcontinue 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 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 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. camels!!! iconic 🐪
  • 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. that's the whole description. do not use. 🙅‍♀️
  • 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. she's the queen bee of saying yes 💖
  • 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 so this is the section that future-proofs your whole setup and honestly it's giving responsible queen ✨

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. no more ✨outdated tutorial energy✨ in your life.

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 morethan once, where the last instance takes precedence. OPAMCLI is only inspected if --cli is not given.

lowkey the whole thing is: say --cli out loud in your scripts, bestie, and future-you will be obsessed with present-you 🫶

💅 EXIT STATUS 💅

ok so before we get into the numbers, there's one lil exception and it's giving main character energy: the exec command does not play by these rules. It returns 127 if the command wasn't found or couldn't be executed, and otherwise it returns the command's own exit value. periodt.

Now the codes, bestie:

  • 0 — Success 🎉 or true for boolean queries.
  • 1 — False. Comes back 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 to an invalid context (e.g. a file that isn't in the format we expected). 🫠
  • 5 — Not found. You asked for something (package, version, repository, etc.) and it just… wasn't there. 💀
  • 10 — Aborted. The operation needed confirmation and you didn't give it.
  • 15 — Couldn't acquire the locks required for the operation. 🔒
  • 20 — There's literally no solution to the user request. This happens when, say, you try to install two packages that hate each other.
  • 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. Could be an error in the packages, or an incompatibility with your system. This can be a partial error.
  • 40 — Sync error. Couldn't fetch some remotes from the network. Also can be a partial error.
  • 50 — Configuration error. Opam or your system config doesn't allow the operation and needs fixing.
  • 60 — Solver failure. The solver failed to return a sound answer. Could be a broken external solver, or an error in solver configuration.
  • 99 — Internal error. Something went wrong, most likely a bug in opam itself. 🙈
  • 130 — User interrupt. SIGINT was received, generally because the user pressed 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).
no cap, that list really does have 0 in it twice, and 123, 124, 125 sitting right at the bottom. we don't make the rules, we just report them faithfully. ✨

📚 FURTHER DOCUMENTATION 📚

See https://opam.ocaml.org/doc. that's it, that's the link, go read, it's giving well-documented queen 💖

👑 AUTHORS 👑

the icons who made this happen, the literal founding mothers and fathers of your favourite package manager:

  • 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>

periodt. absolute legends, every single one. 🎀

🌈 SEE ALSO 🌈

iya, iykyk 🦋

🐛 BUGS 🐛

found something cursed? Check bug reports at https://github.com/ocaml/opam/issues. they're waiting for you bestie, go file it 🫶

okay that's the whole page!! this was Opam 2.6.1, from the OPAM-UNPIN(1) manual page — go forth and unpin responsibly, mwah 💅✨🌸

📦 where this page comes from