Skip to content

GHC 8.6.3 boot libraries missing from Hackage #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
6 tasks
RyanGlScott opened this issue Dec 20, 2018 · 3 comments
Closed
6 tasks

GHC 8.6.3 boot libraries missing from Hackage #203

RyanGlScott opened this issue Dec 20, 2018 · 3 comments
Assignees

Comments

@RyanGlScott
Copy link

The following boot libraries (which are bundled with GHC 8.6.3) appear to be missing from Hackage:

  • ghc-8.6.3
  • ghc-boot-8.6.3
  • ghc-boot-th-8.6.3
  • ghc-heap-8.6.3 (blocked on cabal bug)
  • ghci-8.6.3
  • libiserv-8.6.3

See also:

@hvr hvr self-assigned this Jan 20, 2019
@RyanGlScott
Copy link
Author

I hate to be a bother about this, but can something be done about this issue (and the litany of other similar issues)? It's extremely annoying not being able to look up the Haddocks for the latest ghc release online—I have to resort to Hackage mirrors in order to accomplish this.

Moreover, there's yet another more recent release of ghc (8.6.4) than the one this issue is about. I'm hesitant to open another issue about it if it's just going to clog up the issue tracker unresolved, however.

If there's anything that someone like me can do to help move this along, please let me know. I'm keen to get a resolution on this.

@RyanGlScott
Copy link
Author

RyanGlScott commented Apr 15, 2019

I've just discovered that these libraries are on Stackage:

This means that I can at least find the Haddocks somewhere online, which is the original reason I opened this issue. Closing.


EDIT: And now those links are gone too. Ugh.

@hvr
Copy link
Contributor

hvr commented Apr 16, 2019

@RyanGlScott

Moreover, there's yet another more recent release of ghc (8.6.4) than the one this issue is about. I'm hesitant to open another issue about it if it's just going to clog up the issue tracker unresolved, however.

For the record, I did actually finally get around to deal with those on Sunday evening (a day before you gave up and closed everything...):

And I'll slowly work my way backwards to fill up the gaps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants