#2630: installed packages should have a src-dirs field, for access to optionally
installed sources
------------------------------+---------------------------------------------
Reporter: claus | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: _|_
Component: GHC API | Version: 6.9
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Unknown/Multiple
Os: Unknown/Multiple |
------------------------------+---------------------------------------------
Comment (by simonmar):
Replying to [comment:8 claus]:
>
> Interesting. From `--show-iface`, I got the impression that cross-
package imports weren't tracked?
Try it with 6.10.
> There is no guarantee that all installed packages were haddocked. These
days, one is locked into a specific haddock version, but I used to
experiment with several. When developing packages, I change and reinstall
them often, and I do sometimes keep separate package versions installed
with separate compiler versions, so I'd have to reconstruct the exact
package version and configuration options before trying to add haddocks.
If one wanted to apply the haddock shipping with one version of ghc to
sources hosted in another version of ghc, one would need access to the
sources.
Right, but it's not just the sources - as you say, you need to construct
the exact package version and config, so you'd need some kind of
preprocessed sources and someone has to know exactly how to invoke Haddock
(Cabal doesn't - it knows about Cabal packages, not source caches).
> > Sure you can put sources in your import path and then GHC will pick
them up instead of the package modules, no -fforce-recomp necessary. But
I think you're forgetting about the package metadata again - just having
the sources won't be enough in many cases.
>
> I'm not that forgetful;-) cabal calls `ghc --make` after setting things
up, and at that stage, Ghc Api clients either have a chance, or they won't
work with any form of the source.
I'm afraid I just don't have a clue what you're talking about! What GHC
API clients? A chance to do what? Cabal doesn't invoke any GHC API
clients other than GHC.
If you want to make some progress here, you'll have to provide a
compelling use case, and describe it in very concrete terms. Without
that, there's a danger that we'll provide something that nobody wants or
can use.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2630#comment:9>
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
