Skip to content
Duniverse is the spice of OCaml build life
OCaml Other
  1. OCaml 99.5%
  2. Other 0.5%
Branch: master
Clone or download
NathanReb Merge pull request #62 from Julow/fix-ls-remote
Improve parsing of git ls-remote
Latest commit d691b89 Aug 28, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.dockerfiles Check dune-project and duniverse.opam are in sync in CI Jul 10, 2019
bin Add update command to update commit hash in dune-get files Jul 18, 2019
cli Path pin local packages when initializing duniverse Aug 22, 2019
doc Draft a new spec for duniverse Jun 5, 2019
examples
lib Format Aug 28, 2019
stdune Mark stdune as a vendored directory Jul 30, 2019
test Format Aug 28, 2019
.docker.sh Use a separate build and image to check formatting Apr 26, 2019
.gitignore Add gitignore rules for generated files and dirs in examples Jul 4, 2019
.ocamlformat
.travis.yml Use a separate build and image to check formatting Apr 26, 2019
CHANGES.md Initial import of a Duniverse tool skeleton Jun 15, 2018
LICENSE.md Initial import of a Duniverse tool skeleton Jun 15, 2018
Makefile Setup ocamlformat Apr 23, 2019
README.md Checkout source repos to the previously resolved commit Jul 18, 2019
dune Mark stdune as a vendored directory Jul 30, 2019
dune-project Fix dune-project according to latest opam file changes Jul 19, 2019
duniverse.opam sync Aug 16, 2019

README.md

duniverse -- the spice of OCaml build life

This is an experimental vendoring system for Dune. Not for public consumption just yet.

Please see the manual pages for an explanation of how to use the tool:

Contact @avsm if you have any queries.

Manual Pages

duniverse

NAME
       duniverse - the spice of build life

SYNOPSIS
       duniverse COMMAND ...

DESCRIPTION
       The duniverse tool provides a convenient interface to bridge the opam
       package manager with having a local copy of all the source code
       required to build a project using the dune build tool.

       It works by analysing opam package metadata and calculating a set of
       git tags that can be cloned into the local repository into a
       duniverse/ subdirectory. Once the external code has been pulled into
       the repository, a single dune build command is sufficient to build the
       whole project in a standalone fashion, without opam being required.
       This is a particularly convenient way of publishing CLI tools to users
       who do not need the full power of opam.

       You can access the functionality directly via the duniverse-init,
       duniverse-opam-install and duniverse-pull commands,

       Also see https://github.com/avsm/platform for an example of a fully
       bootstrapping use of this tool.

COMMANDS
       init
           analyse opam files to generate an initial dune-get

       opam-install
           install packages that are not duniverse-compatible via opam

       pull
           fetch the latest archives of the vendored libraries

       update
           update the commit hash corresponding to the tracked branch/tag for
           each source dependency

COMMON OPTIONS
       --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.

       --version
           Show version information.

SEE ALSO
       dune(1), git(1), opam(1)


You can’t perform that action at this time.