Skip to content

Commit e58e495

Browse files
committed
Remove mention of Cabal in drop-packages
As described in the resolution to #5707, Cabal is no longer included in snapshots, so dropping it has no effect.
1 parent 88011fa commit e58e495

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

doc/yaml_configuration.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -256,19 +256,22 @@ be included in our package. This can be used for a few different purposes, e.g.:
256256

257257
* Ensure that packages you don't want used in your project cannot be used in a
258258
`package.yaml` file (e.g., for license reasons)
259-
* Prevent overriding of a global package like `Cabal`. For more information, see
260-
Stackage issue
261-
[#4425](https://github.com/commercialhaskell/stackage/issues/4425)
262259
* When using a custom GHC build, avoid incompatible packages (see this
263260
[comment](https://github.com/commercialhaskell/stack/pull/4655#issuecomment-477954429)).
264261

265262
~~~yaml
266263
drop-packages:
267-
- Cabal
268264
- buggy-package
269265
- package-with-unacceptable-license
270266
~~~
271267

268+
!!! note
269+
270+
Note: in older LTSs, it used to be handy to drop Cabal for reasons listed in Stackage
271+
issue [#4425](https://github.com/commercialhaskell/stackage/issues/4425). However, since
272+
XXX FIXME XXX, Cabal is not included in resolvers, so dropping Cabal no longer has any
273+
effect.
274+
272275
### user-message
273276

274277
If present, specifies a message to be displayed every time the configuration is

0 commit comments

Comments
 (0)