On Mon, May 25, 2020 at 2:52 PM Matthias Kilian wrote:
> > I know why GHC behaves this way, but this property turns minor updates
> > into major events.
>
> Should we do an experiment and try to get rid of MODGHC_PACKAGE_KEY?
I expect we'd trade an obvious and quick failure for a delayed and
Hi,
On Sun, May 24, 2020 at 04:07:50PM -0700, Greg Steuck wrote:
> I only now realized how obnoxious version keying property of cabal is
> when applied to ports. A full-tree ghc upgrade is OK, I expect to
> touch everything. But updating a single library close to the bottom of
> dependency graph
Hi Matthias,
I only now realized how obnoxious version keying property of cabal is
when applied to ports. A full-tree ghc upgrade is OK, I expect to
touch everything. But updating a single library close to the bottom of
dependency graph is not fun all.
Say I updated devel/hs-dlist. It's a
