cabal-plan
cabal-plan copied to clipboard
haskell-hvr
Library and utility for processing cabal's plan.json file
It would be good if the help texts contained some example uses. I fail to discover how to invoke `cabal-plan` to get my license report. This is what I tried:...
Implementation idea is to re-use printing logic from `dumpPlanJson` and filtering the existing `PlanJson` to only contain packages that have in some dependency closure the given dependency. Implementation details: uses...
I'm trying out `cabal-plan`'s `license-report` command and I happened to notice this in the output: ``` WARNING: couldn't find metadata for mattermost-api-50200.14.0 ``` The `mattermost-api` package is a direct dependency...
For further processing, _e.g._, fetching all the license texts to build a `license.txt` file, it would be great if `cabal-plan` could emit the license-report as JSON. Would it be possible...
Similar to `nix`, add `why-depends` command, to show why you depend on a package. Workflow: ```bash $ cabal-plan why-depends exe:foo containers └─ foo-1.0 [foo-1.0:exe:"foo"] └─ some-package-2.7.1 └─ containers-0.6.2.1 ┄┄ ```...
In projects with multiple local packages, when you bump the version numbers on them and one depends on the other, the generated license report will show the License Id and...
Either in the license-report.md or separately, include a list of the distinct licenses in the dependency list. It might look something like this: > - [`BSD-2-Clause`](http://hackage.haskell.org/package/concurrent-output-1.10.21/src/LICENSE) > - [`BSD-3-Clause`](http://hackage.haskell.org/package/base-4.20.0.0/src/LICENSE) >...
`printInfo` uses `putStrLn`, so it already has the requisite trailing newline. The extra `putStrLn` just adds an additional blank line. Using a mix of automated diffing and manual editing to...
Metadata
Owner
Metadata
Library and utility for processing cabal's plan.json file