Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • GHC GHC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4,865
    • Issues 4,865
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 461
    • Merge requests 461
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Glasgow Haskell Compiler
  • GHCGHC
  • Issues
  • #21164
Closed
Open
Created Mar 04, 2022 by Matthew Pickering@mpickeringDeveloper

hadrian bindist documentation directory structure differences

There are a few inconsistencies with the hadrian vs make bindists which I will document here and then we can decide if we do anything about them.

  • hadrian puts docs in docs rather than doc.
  • hadrian puts the pdf documentation in a pdfs folder but make puts the pdfs in the doc folder (one level up)
  • hadrian calls the Haddock html documentation Haddock, which is consistent with the output name (as declared by utils/haddock/doc/conf.py) but make puts it in a folder called haddock (lower case).

At the moment in !7679 (closed) I modified distrib/mkDocs/mkDocs to just look in the right places in the hadrian bindist.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking