1dune-promote(1)                   Dune Manual                  dune-promote(1)
2
3
4

NAME

6       dune-promote - Promote files from the last run
7

SYNOPSIS

9       dune promote [OPTION]...
10

DESCRIPTION

12       Considering all actions of the form (diff a b) that failed in the last
13       run of dune, dune promote does the following: If a is present in the
14       source tree but b isn't, b is copied over to a in the source tree. The
15       idea behind this is that you might use (diff file.expected
16       file.generated) and then call dune promote to promote the generated
17       file.
18

OPTIONS

20       -f, --force
21           Force actions associated to aliases to be re-executed even if their
22           dependencies haven't changed.
23
24       --help[=FMT] (default=auto)
25           Show this help in format FMT. The value FMT must be one of `auto',
26           `pager', `groff' or `plain'. With `auto', the format is `pager` or
27           `plain' whenever the TERM env var is `dumb' or undefined.
28
29       --version
30           Show version information.
31

COMMON OPTIONS

33       These options are common to all commands.
34
35       --auto-promote
36           Automatically promote files. This is similar to running dune
37           promote after the build.
38
39       --build-dir=FILE (absent DUNE_BUILD_DIR env)
40           Specified build directory. _build if unspecified
41
42       --config-file=FILE
43           Load this configuration file instead of the default one.
44
45       --debug-backtraces
46           Always print exception backtraces.
47
48       --debug-dependency-path
49           In case of error, print the dependency path from the targets on the
50           command line to the rule that failed.
51
52       --debug-findlib
53           Debug the findlib sub-system.
54
55       --default-target=TARGET
56           Set the default target that when none is specified to dune build.
57           It defaults to @@default.
58
59       --dev
60           Same as --profile dev
61
62       --diff-command=VAL
63           Shell command to use to diff files
64
65       --display=MODE
66           Control the display mode of Dune. See dune-config(5) for more
67           details.
68
69       --ignore-promoted-rules
70           Ignore rules with (mode promote)
71
72       -j JOBS
73           Run no more than JOBS commands simultaneously.
74
75       --no-buffer
76           Do not buffer the output of commands executed by dune. By default
77           dune buffers the output of subcommands, in order to prevent
78           interleaving when multiple commands are executed in parallel.
79           However, this can be an issue when debugging long running tests.
80           With --no-buffer, commands have direct access to the terminal. Note
81           that as a result their output won't be captured in the log file.
82           You should use this option in conjunction with -j 1, to avoid
83           interleaving. Additionally you should use --verbose as well, to
84           make sure that commands are printed before they are being executed.
85
86       --no-config
87           Do not load the configuration file
88
89       --only-packages=PACKAGES
90           Ignore stanzas referring to a package that is not in PACKAGES.
91           PACKAGES is a comma-separated list of package names. Note that this
92           has the same effect as deleting the relevant stanzas from jbuild
93           files. It is mostly meant for releases. During development, it is
94           likely that what you want instead is to build a particular
95           <package>.install target.
96
97       -p PACKAGES, --for-release-of-packages=PACKAGES
98           Shorthand for --root . --only-packages PACKAGE --promote ignore
99           --no-config --profile release. You must use this option in your
100           <package>.opam files, in order to build only what's necessary when
101           your project contains multiple packages as well as getting
102           reproducible builds.
103
104       --profile=VAL
105           Select the build profile, for instance dev or release. The default
106           is dev.
107
108       --root=DIR
109           Use this directory as workspace root instead of guessing it. Note
110           that this option doesn't change the interpretation of targets given
111           on the command line. It is only intended for scripts.
112
113       --verbose
114           Same as --display verbose
115
116       --workspace=FILE
117           Use this specific workspace file instead of looking it up.
118
119       -x VAL
120           Cross-compile using this toolchain.
121

MORE HELP

123       Use `dune COMMAND --help' for help on a single command.
124

ENVIRONMENT

126       These environment variables affect the execution of promote:
127
128       DUNE_BUILD_DIR
129           Specified build directory. _build if unspecified
130

BUGS

132       Check bug reports at https://github.com/ocaml/dune/issues
133
134
135
136Dune 11VERSION11                                               dune-promote(1)