Skip to content

Conversation

bgamari
Copy link
Collaborator

@bgamari bgamari commented Jan 24, 2022

No description provided.

```
This will cause repository X to be consulted first for any given version of a package, but allow other versions to come from Hackage. For example, if `X` contains `A-1` and `A-2`, and Hackage contains `A-2` and `A-3`, then `A-1` and `A-2` will be taken from `X`, but `A-3` can be taken from Hackage. ([Here is the documentation](https://cabal.readthedocs.io/en/3.6/cabal-project.html) for active-repositories; oddly, the list is searched last-to-first.)

We refer to this style of additional repository as a**Hackage overlay**, since it provides a way to _override_ specific versions of packages which appear in Hackage, while using Hackage for everything else normally.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as a**Hackage overlay** => as a **Hackage overlay** (missing space)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cheers!

@cdornan
Copy link
Contributor

cdornan commented Feb 4, 2022

cool!

@cdornan cdornan merged commit 093d1f8 into main Feb 4, 2022
@cdornan cdornan deleted the ghc-x-hackage branch February 4, 2022 03:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants