This repository has been archived by the owner on Aug 2, 2020. It is now read-only.
[WIP] Use Cabal for package data #108
Closed
Conversation
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
|
Never mind, I merged this into I'll close this now -- many thanks again! |
snowleopard
added a commit
that referenced
this pull request
Jan 12, 2016
Doesn't compile yet. [skip ci]
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a work-in-progress branch to fix #18 that I've had sitting around for lack of time. I believe much of the Cabal logic looks pretty good and it ought to produce everything that we need.
What it lacks is a good way to expose the various pieces of
PackageDatawith an oracle such that we maintain minimal rebuilds.I'm putting this here to provide a starting-point for someone wanting to take up this project before I am able to continue it myself.