OPAM-SOURCE(1)

πŸ’– OPAM-SOURCE(1) β€” opam-source πŸ’–

okay bestie, welcome to the opam-source page, straight outta the Opam Manual. this is the one that goes and gets you the source. let's go 🫢


✨ NAME ✨

opam-source β€” Get the source of an opam package. πŸŽ€


🌸 SYNOPSIS 🌸

opam source [OPTION]… PACKAGE

πŸ¦‹ DESCRIPTION πŸ¦‹

So like, what does it actually do? It downloads the source for a given package into a local directory. that's it, that's the whole vibe. you'd do this for development, for bug fixing, or for documentation purposes. local source on your machine, yours to poke at ✨


πŸ’… ARGUMENTS πŸ’…

  • PACKAGE (required, no cap, you literally cannot skip it) β€” a package name, and you can tack an optional version constraint on there. πŸ“

πŸ‘‘ OPTIONS πŸ‘‘

  • --dev-repo β€” grab the latest version-controlled source instead of the release archive. iykyk, sometimes you want the live repo, not the packaged drop.
  • --dir=DIR β€” the directory where the source should get put. your call, bestie. πŸ“
  • --no-checksums β€” do not verify the checksum of downloaded archives. this is equivalent to setting $OPAMNOCHECKSUMS to "true". (yes that's the same as the env var, pick your fighter)
  • --no-switch β€” choose the package without any consideration for the current switch (or any other switch for that matter) β€” no installed packages, no pinned packages, none of it. just the package, raw. ✨
  • --pin β€” pin the package to the downloaded source. see opam pin for the whole story. πŸ“Œ
  • --require-checksums β€” reject installation of packages that don't provide a checksum for the upstream archives. this is equivalent to setting $OPAMREQUIRECHECKSUMS to "true". strict queen behavior πŸ‘‘

🌈 COMMON OPTIONS 🌈

these ones are common to all commands, so they show up everywhere like that one friend in every group photo. πŸ’–

  • --best-effort β€” don't fail if all the requested packages can't be installed; just try to install as many as possible. heads up tho: not all external solvers may support this option (recent versions of aspcud or mccs should). this is equivalent to setting the $OPAMBESTEFFORT environment variable.
  • --cli=MAJOR.MINOR (absent=2.6) β€” use the command-line interface syntax and semantics of MAJOR.MINOR. it's intended for any persistent use of opam (scripts, blog posts, all of it), and any version of opam in the same MAJOR series will behave as for the specified MINOR release. fun fact: this flag was not available in opam 2.0, so if you wanna select the 2.0 CLI you have to set the OPAMCLI environment variable to 2.0 instead of using this parameter.
  • --color=WHEN β€” colorize the output. WHEN must be one of always, never or auto. 🌈
  • --confirm-level=LEVEL β€” confirmation level. LEVEL must be one of ask, no, yes or unsafe-yes. you can specify this more than once. if --yes or --no are also given, the value of the last --confirm-level is what counts. this is equivalent to setting $OPAMCONFIRMLEVEL.
  • --criteria=CRITERIA β€” specify user preferences for dependency solving for this run. it overrides $OPAMCRITERIA, $OPAMFIXUPCRITERIA and $OPAMUPGRADECRITERIA. for 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, bb: 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 messages to stderr. this is equivalent to setting $OPAMDEBUG to "true".
  • --debug-level=LEVEL β€” like --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 β€” print the git version of opam, if it's set (i.e. you're running a development version), and exit. πŸ’€
  • --help[=FMT] (default=auto) β€” show this help in format FMT. 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 manually through opam pin or through opam install DIR. this is equivalent to setting IGNOREPINDEPENDS=true.
  • --json=FILENAME β€” save 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 β€” answer no to all opam yes/no questions without prompting. see also --confirm-level. this is equivalent to setting $OPAMNO to "true".
  • --no-aspcud β€” Removed in 2.1. rip, she's gone πŸ™ˆ
  • --no-auto-upgrade β€” when configuring or updating a repository that's 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 the 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. (no glow-up today πŸ’…)
  • -q, --quiet β€” disables --verbose.
  • --root=ROOT β€” use ROOT as the current root path. this is equivalent to setting $OPAMROOT to ROOT.
  • --safe, --readonly β€” make sure nothing gets automatically updated or rewritten. super 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. this is equivalent to setting the $OPAMSAFE environment variable.
  • --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}%. this is 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. this is 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). this is 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. this is equivalent to setting $OPAMYES to "true".

lowkey that's a lot of flags, but you ate that. 🍽️✨ more parts coming, bestie β€” don't go anywhere πŸ’–


🌸 ENVIRONMENT 🌸

okay bestie so opam reads a whole bunch of environment variables and honestly they're kind of the cheat codes of the whole thing πŸ’– Here's the roster. One thing though β€” if a variable is a boolean, you turn it OFF with "0", "no", "false", or just an empty string, and you turn it ON with "1", "yes", or "true". No in-between, it's giving binary, periodt.

  • OPAMALLPARENS β€” surround all filters with parenthesis. yeah, all of them πŸ’…
  • OPAMASSUMEDEPEXTS β€” see option `--assume-depexts'.
  • OPAMAUTOANSWER β€” internal use only. don't touch, she's not for you πŸ™ˆ
  • 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. lowkey a mouthful but she's doing her best 🫢
  • OPAMBUILDDOC β€” Removed in 2.1. gone, deceased, no longer with us πŸ’€
  • OPAMBUILDTEST β€” Removed in 2.1. same vibe, also gone.
  • OPAMCLI β€” see option `--cli'.
  • OPAMCOLOR β€” when set to always or never, sets a default value for the `--color' option.
  • OPAMCONFIRMLEVEL β€” see option --confirm-level. and bestie, listen: 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, 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. she digs deep, fr fr ⛏️
  • 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. more jobs = more slay πŸ”₯
  • 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. and heads up: OPAMNO is ignored if either OPAMCONFIRMLEVEL or OPAMYES is set. it's giving "she said no but nobody heard her" 😭
  • OPAMNOAGGREGATE β€” with opam admin check, don't aggregate packages.
  • OPAMNOASPCUD β€” Deprecated. we don't stan her anymore, move on πŸ™ˆ
  • 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. like. do not. 🚨
  • 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 falsea timeout is an error. Currently only thebuiltin-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) β€” yes bestie, "one of" really is written twice, it's iconic actually, we keep it 🌈
  • 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). (yep, the double "one of" is back, we love consistency πŸŽ€)
  • 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. that's it. that's the whole description. girl is not to be touched 🚫
  • 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 so this part is important, bestie, 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. Plus, blog posts or other documentation can benefit, as it prevents information from becoming stale. no cap, futureproofing is the vibe πŸ¦‹

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. so yeah, she'll absolutely call you out if you're being weird about it πŸ’…

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. so like, --cli walks in first and OPAMCLI just sits there quietly being the backup dancer πŸ’–


πŸ’– EXIT STATUS πŸ’–

okay bestie listen up, because this is the part where opam tells you exactly how it's feeling when it walks out the door πŸšͺ✨ Every number here is a whole mood, and you gotta know them all.

⚠️ Exception alert!! As an exception to everything listed below, the exec command returns 127 if the command was not found or couldn't be executed, and returns the command's own exit value otherwise. That's it, that's the exception. 🫢
  • 0 β€” Success ✨ or true for boolean queries. We love a happy ending.
  • 1 β€” False. This is what you get 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 doesn't follow the expected format).
  • 5 β€” Not found. You asked for something (package, version, repository, etc.) that just… could not be found 😭.
  • 10 β€” Aborted. The operation needed confirmation and you ✨did not✨ give it.
  • 15 β€” Could not acquire the locks required for the operation πŸ”’.
  • 20 β€” There is no solution to the user request. This can be caused by asking to install two incompatible packages, for example. (enemies to lovers but make it dependency resolution πŸ’”)
  • 30 β€” Error in package definition, or other metadata files. Heads up: 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.
  • 50 β€” Configuration error. Opam or system configuration doesn't allow the operation, and needs fixing πŸ› οΈ.
  • 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 πŸ› (not you, bestie, it's not your fault).
  • 130 β€” User interrupt. SIGINT was received, generally due to the user pressing Ctrl+C 🫣.

and then there's this little cluster of codes, also on the list:

  • 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 πŸ“š

Need even more lore? The docs live at https://opam.ocaml.org/doc πŸ¦‹


πŸ‘‘ AUTHORS πŸ‘‘

The absolute icons who built this. Show some respect, they ate πŸ’…βœ¨

  • 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 main character. Go read it. iykyk 😌

πŸ› BUGS πŸ›

Found something cursed? Check bug reports at https://github.com/ocaml/opam/issues πŸ’€ We love a good issue thread fr fr.


and that's the whole page, bestie!! πŸŽ€ This one came from Opam 2.6.1, filed as OPAM-SOURCE(1) β€” the date line got cut off in the original, so just know it's the version on the tin ✨ Go forth and opam source something iconic πŸŒΈπŸ«ΆπŸ’œ

πŸ“¦ where this page comes from