<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coq/dune-workspace, branch master</title>
<subtitle>The formal proof system</subtitle>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/'/>
<entry>
<title>[dune] Refactor files following advice from upstream.</title>
<updated>2018-10-05T12:22:02+00:00</updated>
<author>
<name>Emilio Jesus Gallego Arias</name>
</author>
<published>2018-10-04T17:05:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=edaf8d0a34993ac5fab373128a27417a620643d4'/>
<id>edaf8d0a34993ac5fab373128a27417a620643d4</id>
<content type='text'>
After some discussion upstream, I think that for the current a
multi-package setup in a single repository this setup saves a bit
work.

The most problematic bit is the `-rectypes` flag; its status is not
saved per-library so we must either duplicate the flags in the coqide
scope (scope == dune-project file), or unify its scope with Coq. We do
this last option as this seems like the easiest thing for now.

Changes:

- Move coqide.opam file to the root, use a single scope/`dune-project` file.
- Remove `dune-workspace`, this should be owned by the developer / user.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
After some discussion upstream, I think that for the current a
multi-package setup in a single repository this setup saves a bit
work.

The most problematic bit is the `-rectypes` flag; its status is not
saved per-library so we must either duplicate the flags in the coqide
scope (scope == dune-project file), or unify its scope with Coq. We do
this last option as this seems like the easiest thing for now.

Changes:

- Move coqide.opam file to the root, use a single scope/`dune-project` file.
- Remove `dune-workspace`, this should be owned by the developer / user.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge PR #8579: [dune] [merlin] Fix some usability issues.</title>
<updated>2018-10-01T13:03:49+00:00</updated>
<author>
<name>Maxime Dénès</name>
</author>
<published>2018-10-01T13:03:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=c0c3d7f8953323cd5613b0f6c3217f1451a5a060'/>
<id>c0c3d7f8953323cd5613b0f6c3217f1451a5a060</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[dune] Enable warning 60 [unused local module]</title>
<updated>2018-09-29T16:39:07+00:00</updated>
<author>
<name>Emilio Jesus Gallego Arias</name>
</author>
<published>2018-09-29T16:39:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=f4e53e23a060f4d57566fc2cc7bd95fd893a7fe8'/>
<id>f4e53e23a060f4d57566fc2cc7bd95fd893a7fe8</id>
<content type='text'>
This corrects a discrepancy with the make-based system.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This corrects a discrepancy with the make-based system.
</pre>
</div>
</content>
</entry>
<entry>
<title>[dune] [merlin] Fix some usability issues.</title>
<updated>2018-09-27T17:58:54+00:00</updated>
<author>
<name>Emilio Jesus Gallego Arias</name>
</author>
<published>2018-09-27T14:39:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=f0c7587ea53b855ca58ce73d3e25f7e81215a722'/>
<id>f0c7587ea53b855ca58ce73d3e25f7e81215a722</id>
<content type='text'>
As suggested on Gitter by @maximedenes we improve documentation and
update Kernel's `.merlin` so it actually reports on the stricter set
of warnings.

We also set the language version to the proper one so users will get a
better error message [the fact that we can use `(env_var ...)` with
the wrong Dune version is a Dune bug indeed].
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
As suggested on Gitter by @maximedenes we improve documentation and
update Kernel's `.merlin` so it actually reports on the stricter set
of warnings.

We also set the language version to the proper one so users will get a
better error message [the fact that we can use `(env_var ...)` with
the wrong Dune version is a Dune bug indeed].
</pre>
</div>
</content>
</entry>
<entry>
<title>[dune] [ci] Fix and test release profile + use 1.1 dune-workspace</title>
<updated>2018-09-06T18:05:02+00:00</updated>
<author>
<name>Emilio Jesus Gallego Arias</name>
</author>
<published>2018-09-03T13:29:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=69e2490396c1f664350a957149d94ac9894d3c23'/>
<id>69e2490396c1f664350a957149d94ac9894d3c23</id>
<content type='text'>
Dune 1.1 allows us to define the `env` flags in the workspace file,
which is a better place than the current situation.

Along the way, We fix the build flags for release mode [missing
`-rectypes` and add a `release` build profile CI job.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Dune 1.1 allows us to define the `env` flags in the workspace file,
which is a better place than the current situation.

Along the way, We fix the build flags for release mode [missing
`-rectypes` and add a `release` build profile CI job.
</pre>
</div>
</content>
</entry>
</feed>
