File tree Expand file tree Collapse file tree 2 files changed +16
-4
lines changed Expand file tree Collapse file tree 2 files changed +16
-4
lines changed Original file line number Diff line number Diff line change
1
+ synopsis: standalone tests for cabal init
2
+ packages: cabal-install
3
+ prs: #7424
4
+ issues: #7410
5
+
6
+ description: {
7
+ - changes the behaviour of the --tests flag for cabal init,
8
+ see https://github.com/haskell/cabal/issues/7410#issuecomment-849913926
9
+ - adds a new value TestSuite for the PackageType type
10
+ }
Original file line number Diff line number Diff line change @@ -47,20 +47,22 @@ The ``cabal init --interactive`` command is interactive. If we answer
47
47
1) Executable
48
48
2) Library
49
49
3) Library and Executable
50
+ 4) Test suite
50
51
Your choice?
51
52
...
52
53
53
54
One of the important questions is whether the package contains a library
54
55
and/or an executable. Libraries are collections of Haskell modules that
55
56
can be re-used by other Haskell libraries and programs, while executables
56
- are standalone programs.
57
+ are standalone programs. Test suites can both depend on a library or be
58
+ standalonely generated.
57
59
58
60
For the moment these are the only choices. For more complex packages
59
- (e.g. a library and multiple executables or test suites ) the ``.cabal ``
61
+ (e.g. a library and multiple executables) the ``.cabal ``
60
62
file can be edited afterwards.
61
63
62
- After you make your selection (executable; library; or: library
63
- and executable) cabal asks us a number of questions starting with
64
+ After you make your selection (executable; library; library
65
+ and executable; or: test suite ) cabal asks us a number of questions starting with
64
66
which version of the cabal specification to use, our package's name
65
67
(for example, "proglet"), and our package's version.
66
68
You can’t perform that action at this time.
0 commit comments