| commit | 65f13c74166529bfe50dbb52aa4c4274882a3b65 | |
| author | Andreas Abel <andreas.abel@ifi.lmu.de> | |
| Sat, 25 Feb 2023 00:51:45 +0000 (25 01:51 +0100) | ||
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | |
| Sat, 25 Feb 2023 07:20:32 +0000 (25 07:20 +0000) | ||
| tree | 9e65c066c133c173e13879c59c0e3e6a8cb1d7f4 | treesnapshot (tar.gz zip) |
| parent | db03fe147fc70f7650791b5aa770a9ec93666a25 | commitdiff |
Fix #8756: doc: `extra-source-files` are tracked by `cabal build` (#8765)
Changing a file from `extra-source-files` causes `cabal build` to
reevaluate the build plan, judging from the following behavior.
```console
$ cabal build
...
$ cabal build
Up to date
# Make a change to any of the extra-source-files, e.g. Foo.txt
$ cabal build
...
In order, the following would be built (use -v for more details):
- ... (lib) (file Foo.txt changed)
...
```
One notes here that the 3rd `cabal build` does not just output "Up to date".
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit fdcf77b2e6d70a665ef4c2fc0c08bd850ab8114b)
Changing a file from `extra-source-files` causes `cabal build` to
reevaluate the build plan, judging from the following behavior.
```console
$ cabal build
...
$ cabal build
Up to date
# Make a change to any of the extra-source-files, e.g. Foo.txt
$ cabal build
...
In order, the following would be built (use -v for more details):
- ... (lib) (file Foo.txt changed)
...
```
One notes here that the 3rd `cabal build` does not just output "Up to date".
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit fdcf77b2e6d70a665ef4c2fc0c08bd850ab8114b)
| doc/cabal-package.rst | diffblobblamehistory |