In reply to @maralorn:maralorn.de
catsarecute: Unless the override is very nix specific we normally don’t accept patches which don’t have open PR upstream. So basically most of what would be done from our side is already been taken care of.

In reply to @b:chreekat.net
yeah, speaking as somebody who was a GSOC mentor for Haskell a couple years ago, I would actually reconsider skipping out this year depending on what developed here. :) Assuming it's not too late to get registered as a mentor for this year..

From https://summer.haskell.org/ideas.html

This is not an all-inclusive list, so you can apply for projects not in this list and we will try our best to match you with a mentor.

we autogenerate expressions

And as a result many of the broken ones are a doJailbreak away from building.
(Random idea: would automatically trying jailbreak = true on the failing packages as part of the Stackage bump workflow be worth doing?)

In reply to @maralorn:maralorn.de
catsarecute: Unless the override is very nix specific we normally don’t accept patches which don’t have open PR upstream. So basically most of what would be done from our side is already been taken care of.

In reply to @maralorn:maralorn.de
That being said there are certainly a lot of things that could be improved in our setup. I am just not sure if we can manage to bring in GSoC form.

Ah I see, that makes sense. I didn’t realize how much of the set was autogenerated from Hackage.

Out of curiosity then, what parts of the current Haskell packaging setup in nixpkgs do you feel are the roughest right now? I’d be interested in contributing around there.