Include info needed to build backpack-using packages in plan.json#11412
Draft
shlevy wants to merge 1 commit intohaskell:masterfrom
Draft
Include info needed to build backpack-using packages in plan.json#11412shlevy wants to merge 1 commit intohaskell:masterfrom
shlevy wants to merge 1 commit intohaskell:masterfrom
Conversation
Author
|
This is a draft while I confirm this info is sufficient and then I’ll do all the code formatting and changelog etc. |
Author
|
This did turn out to be the info I needed, but it also turns out that haskell.nix vendors its own version of ProjectPlanOutput.hs. I’m happy to clean this up if the maintainers want it, but it’s no longer directly valuable to me. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please read Github PR Conventions and then fill in one of these two templates.
This PR modifies behaviour or interface
Include the following checklist in your PR:
significance: significantin the changelog file.