Hey all, I mentioned (on the long SLURP thread) that I was thinking
about a general proposal for provenance-qualified dependencies to
reduce coupling in the haskell ecosystem. Having worked it out a bit,
I think the bigger win is it also provides a way to specify
dependencies on git repos, etc., which has been an oft-requested
feature.
I don't want to submit it as an ecosystem proposal proper without
further polish, and I held off on bugging a larger audience of cabal
folks until the 2.2 branch was cut. So now I'm passing this along for
further comment and polish before I make a real proposal:
https://github.com/gbaz/ghc-proposals/blob/patch-1/proposals/0000-provenanc…
There's no urgency, but it would be good to get some feedback in the
next few weeks if possible.
Cheers,
Gershom
Hi all,
Oleg mentioned to me on Reddit that a 2.2 branch has been cut for Cabal,
and recommended we try to upgrade Stack to it. I'm sharing information here
on that process in case it's useful to others, either as feedback on the
API changes, or help for others going through similar upgrades. If anyone
would rather that I do or do not post such reports in the future, let me
know.
I've opened a PR for this change[1], which currently is a single commit[2].
As you can see from the change to stack.yaml[3], I needed to refer to the
commit of Cabal in question, and turn on `allow-newer` for some packages
(cabal-doctest and http-api-data) with restrictive upper bounds on Cabal.
Both of these packages compiled without issue.
No change was necessary to Stack's Setup.hs file.
Most of the changes so far were compile-time errors, which is a Good Thing.
Changes I had to make:
* The build type is no longer a Maybe field. (As a user: this is a nice
change, no longer a need to guess about what a Nothing value means.)
* There are now two License types, the original one and the SPDX variant. I
don't understand what this change is about, some further explanation in the
docs or the ChangeLog would definitely be appreciated. But hacking my way
through the types seems to have worked.
* Parsing a package description now works on a ByteString instead of a
String. This allowed me to remove some UTF8 conversion and BOM-stripping
code, which is very nice.
* The new parsing API exposes the cabal file version when that prevented
the parse (at least, that's my understanding). The changes to accommodate
the new API were relatively trivial, so another +1 here.
* Also: getting file position information for warnings and errors is _very_
nice. +1
I haven't done extensive testing yet, but I've so far only found one bug
due to runtime changes: the behavior of allBuildInfo has changed to now
include non-buildable components. This resulted in some confusion until I
reviewed the changelog more closely. If I could make a request, it would be
that, in the future, new runtime behavior come with a new function name, to
convert runtime errors into compile time errors. This was _not_ a
particularly difficult issue to work around though, in large part thanks to
the changelog.
I'll continue testing this branch of Stack. Our plans are to merge this to
master, and release Stack 1.7.0 close to the Cabal 2.2 release date.
Michael
[1] https://github.com/commercialhaskell/stack/pull/3878/files
[2]
https://github.com/commercialhaskell/stack/pull/3878/commits/a101341d04213d…
[3]
https://github.com/commercialhaskell/stack/pull/3878/commits/a101341d04213d…
Hi *,
I've just created the branch for the 2.2 Cabal/cabal-install release
[1]. If everything goes according to plan, the final release will be
out approximately in two weeks' time, i.e. around the end of the
month. This is a delay of one month compared with the original plan
shared in the previous status update [2]. Hopefully, this time there
won't be any more additional delays.
Cheers,
Mikhail
[1] https://github.com/haskell/cabal/tree/2.2
[2] https://mail.haskell.org/pipermail/cabal-devel/2017-December/010410.html
