You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The v2-sdist includes a file twice in the tarball #6611 "v2-sdist includes a file twice in the tarball " issue
is fixed as we don't consider only one file list,
not two separate executable and ordinary file lists.
The rationale for above simplification is simple. The only file
Cabal machinery would run is configure script. These
are run with explicit sh program. For package internal scripts,
maintainers should also use interpreters explicitly as well.
Scripts with shebangs are not executable on Windows.
The v1-sdist command is removed, as its functionality is completely
superseded by v2-sdist.
There are no magical 'IO =WithCallStack Prelude.IO alias in Cabal,
as it is hard to get working with GHC-8.12's simplified subsumption.
Accept "linux-androideabi" as an alias for Android
source-repository-package directories aren't local #5586#6915#6917
Concretely these means that compiled source-repository-package entries
used in different projects are stored in the global nix-style store.
Treat pkg:sublib dependency syntax as is in cabal-version: 3.4#6083#6893#6907
In cabal-version: 3.4 cabal files the dependency definition
build-depends: somesublib
is not using in-package sublibraries. You have to be explicit and write
build-depends: thispkg:somesublib
This fixes an issue, where it was impossible to refer to extenral
library, if you had sublibrary of the same name.
Add -fexpose-all-unfoldings to parsec and Cabal in release project #6708
This makes parser faster with acceptable code-size increase.
Fix ghci being launched before other sources are built. #6923
TBW. Related to foreign calls to C-sources.
Use default install directory if not specified #5973#6624
Cabal 3.0.0.0 added the --installdir option to specify the location that
binaries should be installed in. Running a cabal user-config update would
populate the config file with the default value, but the cabal install program
would error if it wasn't set. This change uses the default value that would be
written to the config if its unset, and outputs a warning.
cabal-install currently assumes that the GHC environment files are always located in $HOME/.ghc/.
However, GHC itself doesn't query the home directory directly.
Instead, it uses getAppUserDataDirectory "ghc" which happens to coincide with $HOME/.ghc/ on UNIX systems.
On Windows, however, GHC ends up looking in %APPDATA%/ghc/.
Remove -any and -none syntax for version ranges in cabal-version: 3.4 #6589#6786
Use >=0 (or empty in dependencies) and <0 respectively.
cabal-install can now take into account the presence and visibility of
sublibraries when solving. This also means that, when using cabal-install,
multiple public libraries support is extended to GHCs older than 8.8.
The support is limited to source packages for now.
Text type-class was removed from Cabal, but it still lived in cabal-install.
Now it is finally removed. cabal-install is still using ReadP parsers for various things though.
Use process jobs when spawning subprocesses #6529#6536
Many toolchain tools written for POSIX systems rely on the exec system
call. Unfortunately, it is not possible to implement exec in a
POSIX-compliant manner on Windows. In particular, the semantics of the
exec implementation provided by the widely-used msvcrt C runtime
will cause process's waiting on the exec'ing process to incorrectly
conclude that the process has successfully terminated when in fact it is
still running in another process.
For this reason, the process library exposes the use_process_jobs
flag to use a more strict (although still not POSIX-compliant) mechanism
for tracking process completion.
This is explained in the Process.hs comment
Unfortunately, job support in the process library is currently quite
broken and was only recently fixed. Consequently, we only enable job
object support for process releases >= 1.6.8.
There are no magical 'IO =WithCallStack Prelude.IO alias in Cabal,
as it is hard to get working with GHC-8.12's simplified subsumption.
Accept "linux-androideabi" as an alias for Android
Treat pkg:sublib dependency syntax as is in cabal-version: 3.4#6083#6893#6907
In cabal-version: 3.4 cabal files the dependency definition
build-depends: somesublib
is not using in-package sublibraries. You have to be explicit and write
build-depends: thispkg:somesublib
This fixes an issue, where it was impossible to refer to extenral
library, if you had sublibrary of the same name.
With additions of (public) sublibraries, Dependency type use for multiple needs become painful.
Therefore a new type PackageVersionConstraint was added to serve constraint on package use-case. Dependency type is dependency on a library component, i.e. representing build-depends entry.
Now it re-exports a collection of modules, not individual symbols.
Use process jobs when spawning subprocesses #6529#6536
Many toolchain tools written for POSIX systems rely on the exec system
call. Unfortunately, it is not possible to implement exec in a
POSIX-compliant manner on Windows. In particular, the semantics of the
exec implementation provided by the widely-used msvcrt C runtime
will cause process's waiting on the exec'ing process to incorrectly
conclude that the process has successfully terminated when in fact it is
still running in another process.
For this reason, the process library exposes the use_process_jobs
flag to use a more strict (although still not POSIX-compliant) mechanism
for tracking process completion.
This is explained in the Process.hs comment
Unfortunately, job support in the process library is currently quite
broken and was only recently fixed. Consequently, we only enable job
object support for process releases >= 1.6.8.
Remove AnyVersion and WildcardVersion constructors from Version #6742
Make Version type less "syntactic", i.e. contains less constructors
for semantically same version ranges.
Cabal-QuickCheck package with Arbirary instances #6882#6557#6891
Create Cabal-tree-diff package with ToExpr instances #6789
Cabal.Distribution.Compiler: add Traversable instance for PerCompilerFlavor #6763
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We forget to update changelog as we go (especially myself).