Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haddock docs are not relocatable in Windows #143

Closed
bos opened this issue May 24, 2012 · 3 comments
Closed

haddock docs are not relocatable in Windows #143

bos opened this issue May 24, 2012 · 3 comments

Comments

@bos
Copy link
Contributor

bos commented May 24, 2012

(Imported from Trac #150, reported by eivuokko on 2007-08-23)

Haddock docs are not installed sensibly in Windows. They go under Common Files, which is silly; Their path doesn't contain compiler version, which makes it hard to install docs for same package version installed for different compilers/versions and they are not relocatable because

  • default uses absolute paths for references
  • with a lot of work they can refer to each other via relative paths, but ghc installation isn't installed in similar fashion. And then all packages must also be installed into same prefix. (ie user-only vs admin installs)
@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by @dcoutts on 2007-08-23)

Changing the default location is easy see Distribution.Simple.InstallDirs?.

Making the docs relocatable is hard.

Fixing the default location should be done for cabal 1.2, the other will have to be deferred.

@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by @dcoutts on 2007-08-23)

The default location has been improved. It doesn't contain the compiler however. But you can override that with --docdir=...

Changing summary, priority & difficulty to reflect the remaining part of the problem.

@tibbe
Copy link
Member

tibbe commented May 5, 2014

Closing as there's been no activity in years.

We're cleaning up the bug tracker to make it useful again and are thus closing bugs that haven't seen any activity in a long time. Please re-open (or file a new bug) if the problem reappears.

@tibbe tibbe closed this as completed May 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants