Closed UnkindPartition closed 6 years ago
Should I try to convert that index to a set of source-urls, or to a custom stack snapshot
Probably one of these, whichever you prefer.
There isn't any support in stack or stackage-curator to make direct use of head.hackage. (Requesting fact check, @snoyberg.)
Correct
On Tue, Oct 23, 2018, 5:06 PM Dan Burton notifications@github.com wrote:
Should I try to convert that index to a set of source-urls, or to a custom stack snapshot
Probably one of these, whichever you prefer.
There isn't any support in stack or stackage-curator to make direct use of head.hackage. (Requesting fact check, @snoyberg https://github.com/snoyberg.)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fpco/stackage-curator/issues/67#issuecomment-432260155, or mute the thread https://github.com/notifications/unsubscribe-auth/AADBB5tu4HdYFaiMqurtRRX7mrFhd2sYks5unyJWgaJpZM4X1Uua .
head.hackage provides a custom package index with packages patched to be compatible with the current GHC HEAD: http://head.hackage.haskell.org/
For the stackage-head project, I'd like to use that index together with stackage-curator. Ideally I'd just point stack to that index, but I haven't found an option to do so.
So I was wondering if you have any thoughts or recommendations on the best way to achieve this. Should I try to convert that index to a set of source-urls, or to a custom stack snapshot, or something else?