package opam-client
Client library for opam 2.1
Install
Dune Dependency
Authors
-
VVincent Bernardoff <vb@luminar.eu.org>
-
RRaja Boujbel <raja.boujbel@ocamlpro.com>
-
RRoberto Di Cosmo <roberto@dicosmo.org>
-
TThomas Gazagnaire <thomas@gazagnaire.org>
-
LLouis Gesbert <louis.gesbert@ocamlpro.com>
-
FFabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
-
AAnil Madhavapeddy <anil@recoil.org>
-
GGuillem Rieu <guillem.rieu@ocamlpro.com>
-
RRalf Treinen <ralf.treinen@pps.jussieu.fr>
-
FFrederic Tuong <tuong@users.gforge.inria.fr>
Maintainers
Sources
2.1.0.tar.gz
md5=c48e9f56ad418827e3af37d2415213a4
sha512=c0060e609c49a12dc8f64accef990aa593db818b72df3984fb9b4b22d8678b46c515916c84134a62dab614c716b61788eadc954d295f32c1f27d38aec22b3edf
doc/opam-client/OpamCliMain/index.html
Module OpamCliMain
Source
Handles calling opam plugins (à la git). E.g. opam publish
runs opam-publish
from PATH, with specific addition of OpamPath.plugins_bin and the current switch bin directory).
Note that this does load some configuration and env, but only handles a leading --yes
argument.
Handles flushing buffers and catching exceptions from the main call, including special cases like OpamStd.Sys.Exec
that is expected to do a Unix.exec
, but after all proper cleanup has been done.
Handling of debug JSON output, according to OpamClientConfig.json_out
run default command_list
runs command-line argument parsing and processing of the command
Default entry point with handling of debug finalisers
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>