-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[new release] dune-build-info, dune, dune-configurator, dune-action-plugin, dune-private-libs and dune-glob (2.0.0+draft1) #15158
Conversation
…lugin, dune-private-libs and dune-glob (2.0.0+draft1) CHANGES: - Introduce `alias` and `package` fields to the `rule` stanza. This is the preferred way of attaching rules to aliases. (ocaml/dune#2744, @rgrinberg) - Add field `(optional)` for executable stanzas (ocaml/dune#2463, fixes ocaml/dune#2433, @bobot) - Infer targets for rule stanzas expressed in long form (ocaml/dune#2494, fixes ocaml/dune#2469, @NathanReb) - Indicate the progress of the initial file tree loading (ocaml/dune#2459, fixes ocaml/dune#2374, @bobot) - Build `.cm[ox]` files for executables more eagerly. This speeds up builds at the cost of building unnecessary artifacts in some cases. Some of these extra artifacts can fail to built, so this is a breaking change. (ocaml/dune#2268, @rgrinberg) - Do not put the `<package>.install` files in the source tree unless `-p` or `--promote-install-files` is passed on the command line (ocaml/dune#2329, @diml) - Change `implicit_transive_deps` to be false. Implicit transitive deps now must be manually enabled (ocaml/dune#2306, @rgrinberg) - Compilation units of user defined executables are now mangled by default. This is done to prevent the accidental collision with library dependencies of the executable. (ocaml/dune#2364, fixes ocaml/dune#2292, @rgrinberg) - Enable `(explicit_js_mode)` by default. (ocaml/dune#1941, @nojb) - Add an option to clear the console in-between builds with `--terminal-persistence=clear-on-rebuild` - Stop symlinking object files to main directory for stanzas defined `jbuild` files (ocaml/dune#2440, @rgrinberg) - Library names are now validated in a strict fashion. Previously, invalid names would be allowed for unwrapped libraries (ocaml/dune#2442, @rgrinberg) - mli only modules must now be explicitly declared. This was previously a warning and is now an error. (ocaml/dune#2442, @rgrinberg) - Modules filtered out from the module list via the Ordered Set Language must now be actual modules. (ocaml/dune#2442, @rgrinberg) - Actions which introduce targets where new targets are forbidden (e.g. preprocessing) are now an error instead of a warning. (ocaml/dune#2442, @rgrinberg) - No longer install a `jbuilder` binary. (ocaml/dune#2441, @diml) - Stub names are no longer allowed relative paths. This was previously a warning and is now an error (ocaml/dune#2443, @rgrinberg). - Define (paths ...) fields in (context ...) definitions in order to set or extend any PATH-like variable in the context environment. (ocaml/dune#2426, @nojb) - The `diff` action will always normalize newlines before diffing. Perviousy, it would not do this normalization for rules defined in jbuild files. (ocaml/dune#2457, @rgrinberg) - Modules may no longer belong to more than one stanza. This was previously allowed only in stanzas defined in `jbuild` files. (ocaml/dune#2458, @rgrinberg) - Remove support for `jbuild-ignore` files. They have been replaced by the the `dirs` stanza in `dune` files. (ocaml/dune#2456, @rgrinberg) - Add a new config option `sandboxing_preference`, the cli argument `--sandbox`, and the dep spec `sandbox` in dune language. These let the user control the level of sandboxing done by dune per rule and globally. The rule specification takes precedence. The global configuration merely specifies the default. (ocaml/dune#2213, @aalekseyev, @diml) - Remove support for old style subsystems. Dune will now emit a warning to reinstall the library with the old style subsystem. (ocaml/dune#2480, @rgrinberg) - Add action (with-stdin-from <file> <action>) to redirect input from <file> when performing <action>. (ocaml/dune#2487, @nojb) - Change the automatically generated odoc index to only list public modules. This only affects unwrapped libraries (ocaml/dune#2479, @rgrinberg) - Set up formatting rules by default. They can be configured through a new `(formatting)` stanza in `dune-project` (ocaml/dune#2347, fixes ocaml/dune#2315, @emillon) - Change default target from `@install` to `@all`. (ocaml/dune#2449, fixes ocaml/dune#1220, @rgrinberg) - Include building stubs in `@check` rules. (@rgrinberg, ocaml/dune#2530) - Get rid of ad-hoc rules for guessing the version. Dune now only relies on the version written in the `dune-project` file and no longer read `VERSION` or similar files (ocaml/dune#2541, @diml) - In `(diff? x y)` action, require `x` to exist and register a dependency on that file. (ocaml/dune#2486, @aalekseyev) - On Windows, an .exe suffix is no longer added implicitly to binary names that already end in .exe. Second, when resolving binary names, .opt variants are no longer chosen automatically. (ocaml/dune#2543, @nojb) - Make `(diff? x y)` move the correction file (`y`) away from the build directory to promotion staging area. This makes corrections work with sandboxing and in general reduces build directory pollution. (ocaml/dune#2486, @aalekseyev, fixes ocaml/dune#2482) - `c_flags`, `c_names` and `cxx_names` are now supported in `executable` and `executables` stanzas. (ocaml/dune#2562, @nojb) Note: this feature has been subsequently extended into a separate `foreign_stubs` field. (ocaml/dune#2659, RFC ocaml/dune#2650, @snowleopard) - Remove git integration from `$ dune upgrade` (ocaml/dune#2565, @rgrinberg) - Add a `--disable-promotion` to disable all modification to the source directory. There's also a corresponding `DUNE_DISABLE_PROMOTION` environment variable. (ocaml/dune#2588, fix ocaml/dune#2568, @rgrinberg) - Add a `forbidden_libraries` field to prevent some library from being linked in an executable. This help detecting who accidently pulls in `unix` for instance (ocaml/dune#2570, @diml) - Fix incorrect error message when a variable is expanded in static context: `%{lib:lib:..}` when the library does not exist. (ocaml/dune#2597, fix ocaml/dune#1541, @rgrinberg) - Add `--sections` option to `$ dune install` to install subsections of .install files. This is useful for installing only the binaries in a workspace for example. (ocaml/dune#2609, fixes ocaml/dune#2554, @rgrinberg) - Drop support for `jbuild` and `jbuild-ignore` files (ocaml/dune#2607, @diml) - Add a `dune-action-plugin` library for describing dependencies direcly in the executable source. Programs that use this feature can be run by a new action (dynamic-run <progn> ...). (ocaml/dune#2635, @staronj, @aalekseyev) - Stop installing the `ocaml-syntax-shims` binary. In order to use `future_syntax`, one now need to depend on the `ocaml-syntax-shims` package (ocaml/dune#2654, @diml) - Add support for dependencies that are re-exported. Such dependencies are marked with`re_export` and will automatically be provided to users of a library (ocaml/dune#2605, @rgrinberg) - Add a `deprecated_library_name` stanza to redirect old names after a library has been renamed (ocaml/dune#2528, @diml) - Error out when a `preprocessor_deps` field is present but not `preprocess` field is. It is a warning with Dune 1.x projects (ocaml/dune#2660, @Julow) - Dune will use `-output-complete-exe` instead of `-custom` when compiling self-contained bytecode executables whenever this options is available (OCaml version >= 4.10) (ocaml/dune#2692, @nojb) - Add action `(with-accepted-exit-codes <pred> <action>)` to specify the set of successful exit codes of `<action>`. `<pred>` is specified using the predicate language. (ocaml/dune#2699, @nojb) - Do not setup rules for disabled libraries (ocaml/dune#2491, fixes ocaml/dune#2272, @bobot) - Configurator: filter out empty flags from `pkg-config` (ocaml/dune#2716, @AltGr) - `no_keep_locs` is a no-op for projects that use `lang dune` older than 2.0. In projects where the language is at least `2.0`, the field is now forbidden. (ocaml/dune#2752, fixes ocaml/dune#2747, @rgrinberg) - Extend support for foreign sources and archives via the `(foreign_library ...)` stanza as well as the `(foreign_stubs ...)` and `(foreign_archives ...)` fields. (ocaml/dune#2659, RFC ocaml/dune#2650, @snowleopard) - Add (deprecated_package_names) field to (package) declaration in dune-project. The names declared here can be used in the (old_public_name) field of (deprecated_library_name) stanza. These names are interpreted as library names (not prefixed by a package name) and appropiate redirections are setup in their META files. This feaure is meant to migrate old libraries which do not follow Dune's convention of prefixing libraries with the package name. (ocaml/dune#2696, @nojb) - The fields `license`, `authors`, `maintainers`, `source`, `bug_reports`, `homepage`, and `documentation` of `dune-project` can now be overriden on a per-package basis. (ocaml/dune#2774, @nojb)
The tests part are having a hard time:
|
Commit: f8bd086 A pull request by opam-seasoned @rgrinberg. ☀️ All lint checks passed f8bd086
☀️ Installability check (+6)
|
Should I do a PR restricting all the packages that are not compatible with dune 2.0 or do you want to have a look at all the failures first and do the PR yourself? |
Your help would be appreciated :)
…On Nov 1, 2019, 8:50 PM +0900, Kate ***@***.***>, wrote:
Should I do a PR restricting all the packages that are not compatible with dune 2.0 or do you want to have a look at all the failures first and do the PR yourself?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The custom run on While looking at the errors, this one does seem a little strange. Does this error seem ok to you?
|
Also I'm noticing something: I thought |
It's slightly different: it's required to mark the root of a project in a multi-project workspace. Before, having a file In any case, this only affects users who use a mono-repo style workflow. |
Regarding the |
ok, thanks for the explanation.
Ok so I'm guessing it's a new hard error for dune 2.0. I finished my first pass on the diff and opened #15206, however I've left out a few of the packages with less straightforward errors like this and will open a second PR shortly. |
This looks like a bug in Dune actually, we are looking at it |
Ok, then here are the remaining failures. Tell me if some of them are normal and require the packages to be constrain:
And the weirder for the end:
All of them were compiling fine before and there has been no changes in the opam-repository (same base commit, same dependencies taken in every cases). |
I had a bit of digging at the error in |
for |
That’s the correct behaviour. Note that this can only cause breakage for users that did not commit a dune-project file. In which case dune will interpret the project as using 2.0. Our backwards compatibility policy applies to people that fix the due language version with a dune-project file.
…On Nov 5, 2019, 1:58 AM +0900, Kate ***@***.***>, wrote:
I had a bit of digging at the error in lwt-pipeline and it seems to be linked to the fact that dune used to insert automatically -I ~/.opam/<switch>/lib/result -I ~/.opam/<switch>/lib/seq to the ocamlc/ocamlopt calls and it's no longer the case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Here's the offending dune file:
I had a closer look and I think this is an issue with 0install. The way to fix it is to simply get rid of this |
Hmm, are you sure about this? |
I tried to reproduce this issue but I was only able to reproduce this issue in conjunction with select. Note that casing doesn’t matter here and I can reproduce it with lowercased names. That’s the extent of my certainty.
But really, I’m not sure what’s the correct behaviour here. On one hand, these selected modules are all valid sources. On the other hand they’re sources for a completely different module after selection. So I think the question is what is the most intuitive behavior.
…On Nov 5, 2019, 9:20 PM +0900, Jérémie Dimino ***@***.***>, wrote:
Hmm, are you sure about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Now that you mention it, this |
Ok so |
I'd like to release a new version of irmin-watcher so that we don't end up with an upper bound constraint on dune 2.0 when its merged. What's the right fix here? It looks like a straightforward use of |
For irmin-watcher, I think the fix should be simple and I’ve put up a PR that will make it compatible with dune 2.0 and dune 1.x.
For 0install, the way that should be compatible with dune 1.x and 2.x would be to just list out all the modules.
@diml It seems like we need an explicit modules when we use select with dune 1.x. Unfortunately this module list doesn’t work for 2.0 because it excludes non existent modules. We could allow people to use these module names for exclusions in 2.x. Currently, the way to write a select that is compatible with 2.0 and 1.x is to always write the modules field exhaustively without using OSL.
…On Nov 6, 2019, 2:42 AM +0900, Anil Madhavapeddy , wrote:
I'd like to release a new version of irmin-watcher so that we don't end up with an upper bound constraint on dune 2.0 when its merged. What's the right fix here? It looks like a straightforward use of (select) that is now incompatible with dune 2.0 for some reason...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
There is another solution; the various choices don't have to be proper (library
(name zeroinstall)
(modules_without_implementation feed_provider progress sigs ui)
(libraries curl curl.lwt dynlink lwt_react support yojson
(select dbus.ml from
(obus.network-manager
obus.notification -> dbus.with.ml)
( -> dbus.without.ml)))) This is in fact how I imagined |
Should we just make users follow this convention then? I think it's unlikely they'll think of this themselves otherwise. |
I’ve submitted upstream fixes for 0install and irmin-watcher:
0install/0install#117
mirage/irmin-watcher#25
…On Nov 6, 2019, 5:02 PM +0900, Jérémie Dimino ***@***.***>, wrote:
There is another solution; the various choices don't have to be proper <module-name>.ml files:
(library
(name zeroinstall)
(modules_without_implementation feed_provider progress sigs ui)
(libraries curl curl.lwt dynlink lwt_react support yojson
(select dbus.ml from
(obus.network-manager
obus.notification -> dbus.with.ml)
( -> dbus.without.ml))))
This is in fact how I imagined select would be used initially.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
That would be best yeah. The only thing is that |
FI the PR which removed the list of file names from select ocaml/dune#2506. |
There seems to be a difference in the way we handle symlinks. This is likely due to my change to port dune to use memoization in file tree.
The symlink in minisat for example, is:
$ ls src/
minisat -> minisat-C-1.14.1
minisat-C-1.14.1
…
That indeed seems like something that should be forbidden. I’m actually not sure how the old code allowed this.
|
All the include and missing module errors are accounted for. It's just the lack of dune-project file that is forcing these projects to use |
The rest of the packages should be constrained by #15229. I'll run another global check once this is done and if all is green we can call it successful. |
Ok everything is green now (except some unrelated failures) ... except just one package:
I tested locally and with Could you look into it? |
I think it's the same |
Oh, right, I was looking at the wrong thing in the dune file, my bad. Thanks! |
The Irmin-watcher PR (mirage/irmin-watcher#25) seems to fail on dune 1.11.4 and I won't have time to look at it for a few days, so I just wanted to flag that up -- I'm still not entirely clear what a dune 1.x and 2.x compatible solution for |
I pushed a commit that should fix this issue. Thanks for bringing this to my attention.
…On Nov 7, 2019, 11:48 PM +0900, Anil Madhavapeddy ***@***.***>, wrote:
The Irmin-watcher PR (mirage/irmin-watcher#25) seems to fail on dune 1.11.4 and I won't have time to look at it for a few days, so I just wanted to flag that up -- I'm still not entirely clear what a dune 1.x and 2.x compatible solution for (select) is.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Second draft here: #15261 |
Embed build informations inside executable
CHANGES:
Introduce
alias
andpackage
fields to therule
stanza. This is thepreferred way of attaching rules to aliases. (Add alias field to rules dune#2744, @rgrinberg)
Add field
(optional)
for executable stanzas (Add optional executables dune#2463, fixes executables: (optional) equivalent? dune#2433, @bobot)Infer targets for rule stanzas expressed in long form (Infer rule targets in long-form rule stanzas as well dune#2494, fixes Rule target inferrence doesn't work with write-file dune#2469,
@NathanReb)
Indicate the progress of the initial file tree loading (Show the progress of the file tree scanning dune#2459, fixes dune running in $HOME is super slow dune#2374,
@bobot)
Build
.cm[ox]
files for executables more eagerly. This speeds up builds atthe cost of building unnecessary artifacts in some cases. Some of these extra
artifacts can fail to built, so this is a breaking change. (Build .cmx/.o files more eagerly for executables dune#2268, @rgrinberg)
Do not put the
<package>.install
files in the source tree unless-p
or--promote-install-files
is passed on the command line (opam pin dune fails as dune.install is not promoted dune#2329, @diml)Change
implicit_transive_deps
to be false. Implicit transitive deps now mustbe manually enabled (Change implicit_transive_deps to be false for 2.0 dune#2306, @rgrinberg)
Compilation units of user defined executables are now mangled by default. This
is done to prevent the accidental collision with library dependencies of the
executable. (Mangle compilation units of dune generated modules dune#2364, fixes Add name mangling to dune binaries dune#2292, @rgrinberg)
Enable
(explicit_js_mode)
by default. (Explicit js mode dune#1941, @nojb)Add an option to clear the console in-between builds with
--terminal-persistence=clear-on-rebuild
Stop symlinking object files to main directory for stanzas defined
jbuild
files (Remove compat symlinks for jbuild files dune#2440, @rgrinberg)
Library names are now validated in a strict fashion. Previously, invalid names
would be allowed for unwrapped libraries (Turn a bunch of compatibility warnings into errors dune#2442, @rgrinberg)
mli only modules must now be explicitly declared. This was previously a
warning and is now an error. (Turn a bunch of compatibility warnings into errors dune#2442, @rgrinberg)
Modules filtered out from the module list via the Ordered Set Language must
now be actual modules. (Turn a bunch of compatibility warnings into errors dune#2442, @rgrinberg)
Actions which introduce targets where new targets are forbidden (e.g.
preprocessing) are now an error instead of a warning. (Turn a bunch of compatibility warnings into errors dune#2442, @rgrinberg)
No longer install a
jbuilder
binary. (Good bye jbuilder 👋 dune#2441, @diml)Stub names are no longer allowed relative paths. This was previously a warning
and is now an error (Error when stub names are relative paths dune#2443, @rgrinberg).
Define (paths ...) fields in (context ...) definitions in order to set or
extend any PATH-like variable in the context environment. (Add (paths ...) field to (context ...) definition dune#2426, @nojb)
The
diff
action will always normalize newlines before diffing. Perviousy, itwould not do this normalization for rules defined in jbuild files. (Remove jbuild style diff comparison dune#2457,
@rgrinberg)
Modules may no longer belong to more than one stanza. This was previously
allowed only in stanzas defined in
jbuild
files. (Remove more old jbuild support dune#2458, @rgrinberg)Remove support for
jbuild-ignore
files. They have been replaced by the thedirs
stanza indune
files. (Remove support for jbuild-ignore files dune#2456, @rgrinberg)Add a new config option
sandboxing_preference
, the cli argument--sandbox
,and the dep spec
sandbox
in dune language. These let the user control the level ofsandboxing done by dune per rule and globally. The rule specification takes precedence.
The global configuration merely specifies the default.
(Global sandboxing setting dune#2213, @aalekseyev, @diml)
Remove support for old style subsystems. Dune will now emit a warning to
reinstall the library with the old style subsystem. (Remove support for old style subsystems dune#2480, @rgrinberg)
Add action (with-stdin-from ) to redirect input from
when performing . (Add (with-stdin-from ...) dune#2487, @nojb)
Change the automatically generated odoc index to only list public modules.
This only affects unwrapped libraries ([odoc] module visibility and entry list dune#2479, @rgrinberg)
Set up formatting rules by default. They can be configured through a new
(formatting)
stanza indune-project
(Dune2 formatting dune#2347, fixes dune 2: set up formatting rules by default dune#2315, @emillon)Change default target from
@install
to@all
. (Change the default target to@all
dune#2449, fixes [PROPOSAL] Change the Default Target dune#1220,@rgrinberg)
Include building stubs in
@check
rules. (@rgrinberg, Compile stubs for @check dune#2530)Get rid of ad-hoc rules for guessing the version. Dune now only
relies on the version written in the
dune-project
file and nolonger read
VERSION
or similar files (Simplify the computing of version numbers dune#2541, @diml)In
(diff? x y)
action, requirex
to exist and register adependency on that file. (Improvements to
diff?
semantics dune#2486, @aalekseyev)On Windows, an .exe suffix is no longer added implicitly to binary names that
already end in .exe. Second, when resolving binary names, .opt variants are no
longer chosen automatically. (Cleanup handling of .opt and .exe dune#2543, @nojb)
Make
(diff? x y)
move the correction file (y
) away from the builddirectory to promotion staging area. This makes corrections work with
sandboxing and in general reduces build directory pollution. (Improvements to
diff?
semantics dune#2486,@aalekseyev, fixes [RFC] Better semantic of
diff?
dune#2482)c_flags
,c_names
andcxx_names
are now supported inexecutable
and
executables
stanzas. (Allow c_flags, c_names, cxx_names in executable stanzas dune#2562, @nojb)Note: this feature has been subsequently extended into a separate
foreign_stubs
field. (Add support for foreign libraries dune#2659, RFC [RFC] Foreign libraries dune#2650, @snowleopard)Remove git integration from
$ dune upgrade
(Minor improvements for Build_info and install dune#2565, @rgrinberg)Add a
--disable-promotion
to disable all modification to the sourcedirectory. There's also a corresponding
DUNE_DISABLE_PROMOTION
environmentvariable. (Add --disable-promotion option dune#2588, fix Feature request: CLI flag or env var to disable .merlin generation dune#2568, @rgrinberg)
Add a
forbidden_libraries
field to prevent some library from beinglinked in an executable. This help detecting who accidently pulls in
unix
for instance (Add aforbidden_libraries
field to executable stanzas dune#2570, @diml)Fix incorrect error message when a variable is expanded in static context:
%{lib:lib:..}
when the library does not exist. (Fix incorrect message "unknown macro" dune#2597, fix Improve error message for%{lib:...}
dune#1541,@rgrinberg)
Add
--sections
option to$ dune install
to install subsections of .installfiles. This is useful for installing only the binaries in a workspace for
example. (Add --sections option to install/uninstall dune#2609, fixes dune install ignores the
(vendor)
markers dune#2554, @rgrinberg)Drop support for
jbuild
andjbuild-ignore
files (Move jbuild support into a separate library dune#2607, @diml)Add a
dune-action-plugin
library for describing dependencies direcly inthe executable source. Programs that use this feature can be run by a new
action (dynamic-run ...). (
dune-action-plugin
- expressing dependencies directly in source code dune#2635, @staronj, @aalekseyev)Stop installing the
ocaml-syntax-shims
binary. In order to usefuture_syntax
, one now need to depend on theocaml-syntax-shims
package (Stop installing the ocaml-syntax-shims binary dune#2654, @diml)
Add support for dependencies that are re-exported. Such dependencies
are marked with
re_export
and will automatically be provided tousers of a library (Add re_exports for libraries dune#2605, @rgrinberg)
Add a
deprecated_library_name
stanza to redirect old names after alibrary has been renamed (Add a deprecated_library_name stanza dune#2528, @diml)
Error out when a
preprocessor_deps
field is present but notpreprocess
field is. It is a warning with Dune 1.x projects(Warn about unused preprocessor_deps dune#2660, @Julow)
Dune will use
-output-complete-exe
instead of-custom
when compilingself-contained bytecode executables whenever this options is available
(OCaml version >= 4.10) (Use -output-complete-exe if available dune#2692, @nojb)
Add action
(with-accepted-exit-codes <pred> <action>)
to specify the set ofsuccessful exit codes of
<action>
.<pred>
is specified using the predicatelanguage. (Add (with-exit-codes <pred> <action>) action dune#2699, @nojb)
Do not setup rules for disabled libraries (Fix
@all
alias should only build enabled libraries dune#2491, fixes@all
doesn't work with enabled_if on libraries dune#2272, @bobot)Configurator: filter out empty flags from
pkg-config
(Configurator: fix noisy empty compiler command-line arguments dune#2716, @AltGr)no_keep_locs
is a no-op for projects that uselang dune
older than 2.0. Inprojects where the language is at least
2.0
, the field is now forbidden.(Make no_keep_locs a no-op dune#2752, fixes Delete
(no_keep_locs)
dune#2747, @rgrinberg)Extend support for foreign sources and archives via the
(foreign_library ...)
stanza as well as the
(foreign_stubs ...)
and(foreign_archives ...)
fields.(Add support for foreign libraries dune#2659, RFC [RFC] Foreign libraries dune#2650, @snowleopard)
Add (deprecated_package_names) field to (package) declaration in
dune-project. The names declared here can be used in the (old_public_name)
field of (deprecated_library_name) stanza. These names are interpreted as
library names (not prefixed by a package name) and appropiate redirections are
setup in their META files. This feaure is meant to migrate old libraries which
do not follow Dune's convention of prefixing libraries with the package
name. (Allow top-level libraries in
old_public_name
dune#2696, @nojb)The fields
license
,authors
,maintainers
,source
,bug_reports
,homepage
, anddocumentation
ofdune-project
can now be overriden on aper-package basis. (Allow to set per-package information dune#2774, @nojb)