Unverified Commit e7dfd6d7 authored by Julian Ospald's avatar Julian Ospald 🍵

Change 'optional-packages' default on missing cabal.project

Fixes #6739
parent b89a1c63
......@@ -67,7 +67,7 @@ project are:
.. cfg-field:: optional-packages: package location list (space or comma-separated)
:synopsis: Optional project packages.
:default: ``./*/*.cabal``
:default: empty
Like :cfg-field:`packages`, specifies a list of package locations
containing local packages to be built. Unlike :cfg-field:`packages`,
......@@ -90,13 +90,14 @@ project are:
All local packages are *vendored*, in the sense that if other packages
(including external ones from Hackage) depend on a package with the name
of a local package, the local package is preferentially used. This
motivates the default settings::
of a local package, the local package is preferentially used.
For subdirectories to be considered local packages, the following setting
can be used::
packages: ./*.cabal
optional-packages: ./*/*.cabal
...any package can be vendored simply by making a checkout in the
...then any package can be vendored simply by making a checkout in the
top-level project directory, as might be seen in this hypothetical
directory layout::
......
......@@ -544,9 +544,6 @@ readProjectLocalConfigOrDefault verbosity distDirLayout = do
-- We expect a package in the current directory.
projectPackages = [ "./*.cabal" ],
-- This is to automatically pick up deps that we unpack locally.
projectPackagesOptional = [ "./*/*.cabal" ],
projectConfigProvenance = Set.singleton Implicit
}
......
synopsis: Change 'optional-packages' default to empty, when cabal.project is mising.
issues: #6739
prs: #6740
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment