Mark,
I am working on the (64-bit, but will also be the 32-bit) Windows build(s),
feeling similar to you. I can't offer too much help on Mac-specific issues but
probably have similar questions Windows-related, so we can leverage the
overlap. I'm staying in town over the holiday weekend, so p
(left out the very important "no" in "I have *no* expertise in using ghc in
non-ASCII)
From: ra...@kanonika.com
To: suho...@gmail.com
CC: haskell-platform@projects.haskell.org; randyhask...@outlook.com
Subject: RE: At long last: 2014.2.0.0 Release Candidate 1
Date: Sat, 26 Jul 2014 16:55:01 -070
I have a concern about promoting HP, minghc, and stack all
together on the haskell.org website, without there being any
way to go between them (thinking just the Windows platform
here). Perhaps minghc and stack play well together, but
possibly not stack and HP?
If we want folks to use HP but then
Sven,
Sorry I didn't respond here, but the first two issues are
in the github issues list for haskell-platform, where I have
marked them for 7.10.2 (Windows-specific)
* #191 haddock hard-coded path
* #189 WARNING: cache is out of date:...
For the "missing documentation" issue, I assume you mean
I have the build logs for the Windows builds, if that
helps in the forensics (i.e, if an HP build problem), but
if a similar thing happens in your own sandbox build,
maybe not HP related? However, only the packages
we build in HP are missing the package name annotation,
so perhaps we are missing a
