[sorry about that empty message before; here's what i meant to send]
| Sun Sep 23 05:06:36 PDT 2007 [EMAIL PROTECTED]
| * Fix bug #1725 (Haddock links between packages)
| Resolving this bug is a bit tricky, it boils down to the question:
| Should the
| Haddock links between packages include the package version or not?
Arguably, A's documentation should not break. In principle
you can have many versions of A and B installed, and they
should each have distinct documentation.
If you uninstall B then A breaks anyway, since A depends
on (that version of) B, so you'd better uninstall A.
I suppose A could depend on a *range* of versions of B.
In that case, A would not break if you upgrade, so really A's
documentation should link to any B in that range. Darn I can
see that's hard if you don't want to leave HTML.
if A depends on a specific version of B, so should its docs.
if A depends on any version of B so should its docs.
the 'any version of B' docs could be a virtual page, maintained
by haddock install, silently redirecting to a specific version if
available, and saing 'not installed' otherwise. one could refine
that to ranges by having package docs link to the versions
they depend on, and haddock install turning those into either
indirections or placeholders whenever installing/deinstalling
package docs matching the criteria. haddock install does
not exist, of course?
claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
