<br><br><div class="gmail_quote">On Wed, Apr 22, 2009 at 2:06 PM, Duncan Coutts <span dir="ltr"><<a href="mailto:duncan.coutts@worc.ox.ac.uk">duncan.coutts@worc.ox.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, 2009-04-22 at 11:33 +0200, david48 wrote:<br>
><br>
> The default should at least be consistent among cabal install, runghc<br>
> Setup.hs, installing GHC, Gtk2Hs, and so on.<br>
><br>
> If GHC is installed in /home/myusername/local,<br>
<br>
</div>Where you choose to install ghc is not related.<br>
<div class="im"><br>
> what does cabal install --global ?<br>
<br>
</div>Global always means /usr/local by default, unless you change it in the<br>
cabal config file.<br>
<br>
By default ghc, gtk2hs also install globally in /usr/local (unless you<br>
specify a --prefix.)<br>
<br>
This tradition of global and /usr/local for ./configure scripts is ok,<br>
but for a convenient package manager it's not necessarily ideal.<br>
<div><div></div><div class="h5"><br>
</div></div></blockquote></div>Ubuntu/Debian policy seems to be installation into /var/lib/cabal . So it's clear that the whole hierarchy is managed by single tool cabal. Drawback is that you should add /var/lib/cabal/bin into your PATH.<br>
<br clear="all">-- <br>Victor Nazarov<br><br>