#1878: --print-docdir gives the wrong results in a binary distribution
----------------------+-----------------------------------------------------
Reporter: simonmar | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.8.2
Component: Compiler | Version: 6.8.1
Severity: normal | Resolution:
Keywords: | Difficulty: Easy (1 hr)
Testcase: | Architecture: Unknown
Os: Unknown |
----------------------+-----------------------------------------------------
Changes (by claus):
* cc: claus (added)
Comment:
Replying to [comment:1 duncan]:
> Why do we even have a --print-docdir flag? Documentation is mostly a
property of a package, not of the compiler, unless it refers only to the
ghc user guide.
that was the whole idea. given one ghc/ghci among possibly many installed
ones, find the right version of its user guide, check whether it is
installed locally, give the correct path for the local user guide if it is
installed, or the correct url for the `haskell.org` user guide if it isn't
installed.
for packages, `cabal` and `ghc-pkg` should be able to answer, and perhaps
the user guide should simply be a source-less package? but you still need
to be able to find the right `ghc-pkg` for the `ghc` at hand.
there is a related issue with `runhaskell` (#1281). in short, all ghc
tools need to know which installation they belong to, even after
relocation, and at least one of them needs to be able to tell where to
find the rest of that installation, to get matching tools and docs. it
would be ok if that required a simple post-install step to tell ghc that
it has been relocated, and where everything is.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1878#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
