#1880: Unify flag descriptions to generate both docs and code
----------------------+-----------------------------------------------------
Reporter: simonmar | Owner:
Type: task | Status: new
Priority: normal | Milestone: 6.10 branch
Component: Compiler | Version: 6.8.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Unknown
Os: Unknown |
----------------------+-----------------------------------------------------
Comment (by claus):
ah, so it is the general "how do i find the other parts of myself" issue,
once again?
how about this approach: have `ghc/ghci`, `libdir`, `docdir`, and whatever
else is needed, registered as special "system" packages (or as fields of a
single system package) with `ghc-pkg` during installation (or
post-"install" for tarballs).
then the only thing one needs to know is how to find `ghc-pkg` or its
database, which `ghc`, `ghci`, and `ghc-pkg` seem to be able to do
already. and `ghc-pkg` could be queried for all other tool and library
locations. after something like
`ghc-pkg register --system docdir <path>`,
`ghc-pkg --system docdir`
would yield the last registered location of the docs, if any. and
similarly for finding libdir, etc. the registration/update would be done
by installers, package managers, or users (for tarballs/bootstraps).
does that sound plausible?
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1880#comment:6>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
