Local packages list license file and summary as `*MISSING*`

[sellout]

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 Description on the local dependency as *MISSING*.

Name	Version	SPDX License Id	Description	Also depended upon by
yaya	0.6.2.1	MISSING	MISSING

This is because the newly bumped version hasn’t made it to Hackage yet. But hopefully the info can be gathered from the local package?

[sellout]

And if there’s a mechanism for looking up the info for local packages, then might as well include the license information for the package the report is based on, not just its dependencies.

[sellout]

This has been a bit of annoyance lately because of my CI process (and I’m open to suggestions of how I can improve things on my end).

I commit the license report and include it in my packages’ extra-docs. Then, in CI, I diff the committed license report to make sure it’s up-to-date before publishing a new version of my package.

I set index-state in cabal.project to avoid diffs caused by Hackage changes between CI runs, but I still get occasional failures from things like

diff --git a/containers/docs/license-report.md b/containers/docs/license-report.md
index 7905688..03d2517 100644
--- a/containers/docs/license-report.md
+++ b/containers/docs/license-report.md
@@ -10,7 +10,7 @@ Bold-faced **`package-name`**s denote standard libraries bundled with `ghc-9.10.
 | --- | --- | --- | --- | --- |
 | **`base`** | [`4.20.0.0`](http://hackage.haskell.org/package/base-4.20.0.0) | [`BSD-3-Clause`](http://hackage.haskell.org/package/base-4.20.0.0/src/LICENSE) | Core data structures and operations | *(core library)* |
 | **`containers`** | [`0.7`](http://hackage.haskell.org/package/containers-0.7) | [`BSD-3-Clause`](http://hackage.haskell.org/package/containers-0.7/src/LICENSE) | Assorted concrete container types | `adjunctions`, `bifunctors`, `binary`, `comonad`, `free`, `hashable`, `indexed-traversable`, `invariant`, `kan-extensions`, `lens`, `parallel`, `semigroupoids`, `th-abstraction` |
-| `yaya` | [`0.6.2.3`](http://hackage.haskell.org/package/yaya-0.6.2.3) |  *MISSING* | *MISSING* |  |
+| `yaya` | [`0.6.2.3`](http://hackage.haskell.org/package/yaya-0.6.2.3) | [`AGPL-3.0-or-later`](http://hackage.haskell.org/package/yaya-0.6.2.3/src/LICENSE) | Total recursion schemes. |  |
 
 ## Indirect transitive dependencies
 

because yaya and yaya-containers are in the same repo and yaya-containers depends on yaya, so when I initially publish a new version of yaya, the yaya-containers file is updated to

| `yaya` | [`0.6.2.3`](http://hackage.haskell.org/package/yaya-0.6.2.3) |  *MISSING* | *MISSING* |  |

because the new version of yaya doesn’t yet exist on Hackage. But then some CI run that happens after publishing yaya (often the run on my default branch after merging the PR) fails because the license report now contains

| `yaya` | [`0.6.2.3`](http://hackage.haskell.org/package/yaya-0.6.2.3) | [`AGPL-3.0-or-later`](http://hackage.haskell.org/package/yaya-0.6.2.3/src/LICENSE) | Total recursion schemes. |  |

since the new release of yaya has made it into Hackage in the meantime.

potential workarounds

• --ignore-matching-lines in the diff to overlook differences involving local packages
• post-process the license-report to either complete or erase the license report entries for local packages
• ???