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]... [FILE]...
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
32       -w, --watch
33           Instead of terminating build after completion, wait continuously
34           for file changes.
35

COMMON OPTIONS

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

MORE HELP

138       Use `dune COMMAND --help' for help on a single command.
139

ENVIRONMENT

141       These environment variables affect the execution of promote:
142
143       DUNE_BUILD_DIR
144           Specified build directory. _build if unspecified
145
146       DUNE_PROFILE
147           Build profile. dev if unspecified or release if -p is set.
148
149       DUNE_STORE_ORIG_SOURCE_DIR
150           Store original source location in dune-package metadata
151

BUGS

153       Check bug reports at https://github.com/ocaml/dune/issues
154
155
156
157Dune 11VERSION11                                               dune-promote(1)