<span class="gmail_quote"></span><span class="q"><br>
</span><div><span class="q"><span class="gmail_quote"></span></span><div>*
The &quot;Program Files&quot; folder usually has at least one space in its
path, which could cause a lot of problems for Unix-centric software.
For this reason alone, I always install anything that isn't
Windows-specific into &quot;c:\software&quot; instead of &quot;C:\Program Files.&quot; If
the default prefix is going to be &quot;Program Files&quot; then there should be
a note in the Cabal documentation that the application should expect to
be installed into a directory with spaces in the path.<br>
<br>* Even if a program is written in Haskell and is built with
Cabal, I imagine that people who write Windows Haskell software for non-developers
will not expect users to install the software via Cabal. Instead, they
will provide an MSI with a GUI installer. That means that, for the most
part, the only users of Cabal on Windows will be programmers. So, I
think that the Cabal experience on Windows should be
optimized for us. In particular, if I run &quot;runghc Setup.hs install&quot; when
I am using MSYS Bash, I want the package to install into &quot;/usr/local/&quot;
just like it would on Unix. <br>
<br>* I don't think it makes sense for executable packages to have
&quot;Haskell&quot; in their prefix unless they are explicitly &quot;for Haskell.&quot; For
example, Darcs isn't a Haskell tool; it is a versioning tool that
happens to be implemented in Haskell, so it wouldn't make sense for it
to be installed into &quot;C:\Program Files\Haskell\Darcs-1.0,&quot; just like we
wouldn't want it installed into &quot;C:\Prgoram Files\C#\Darcs-1.0&quot; if it
was written in C#. Conversely, library packages are presumable
Haskell-specific and so it makes sense for them to have &quot;Haskell&quot; in
their prefix.<br>
<br>
Just my 2 cents.<br>
<br>
- Brian<br>
<br>
- Brian<br>
<br>
[1]
<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/functions/shgetfolderpath.asp" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/functions/shgetfolderpath.asp
</a><br>
[2] <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwue/html/ch11b.asp" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwue/html/ch11b.asp
</a><br><span class="sg">
<br>

- Brian<br>
<br>
</span></div><div><span class="e" id="q_10484090db3386d5_6"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">or<br><br>2) C:\Haskell\&lt;package-name&gt;-&lt;version&gt;
<br><br>where &quot;Haskell&quot; could also be &quot;Packages&quot; I guess.
<br><br>-- Daan Leijen<br><br>Brian Smith wrote:<br>&gt; On 6/15/05, *Simon Marlow* &lt;<a href="mailto:simonmar@microsoft.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">simonmar@microsoft.com
</a><br>&gt; &lt;mailto:<a href="mailto:simonmar@microsoft.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">simonmar@microsoft.com
</a>&gt;&gt; wrote:<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; On 15 June 2005 05:49, Brian Smith wrote:<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt; The documentation states in Section 3.1 that the default value of<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt; &quot;prefix&quot; is &quot;/usr/local&quot; on Unix. However, it doesn't specify
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; what the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt; prefix is on Windows. I found that the default value for prefix is:<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp; C:\Program<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt; Files\&lt;package-name&gt;\&lt;compiler-name&gt;-&lt;compiler-version&gt;. For example,
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt; version 1.0 of a package named &quot;Foo&quot; compiled with GHC<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt; 6.5 would have a default prefix of:<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&gt;&nbsp;&nbsp;&nbsp;&nbsp; C:\Program Files\Foo\ghc-6.5<br>&gt;<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; The compiler version is there to avoid conflicts in the case when you
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; have multiple versions of GHC installed and the package is installed for<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; each one.&nbsp;&nbsp;However, I don't think we currently include the compiler &amp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; version in the default $(libdir) on Unix, so whatever we do we should do
<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; it consistently.<br>&gt;<br>&gt;<br>&gt; Okay, that makes more sense to me. However, I think that executables<br>&gt; should go in&nbsp;&nbsp;&quot;C:\Program Files\&lt;package-name&gt;-&lt;package-version&gt;\bin,&quot;
<br>&gt; not &lt;C:\Program<br>&gt; Files\&lt;package-name&gt;\&lt;compiler-name&gt;-&lt;compiler-version&gt;\bin&quot; as they do<br>&gt; currently.<br>&gt;<br>&gt; - Brian<br>&gt;<br>&gt;<br>&gt;<br>&gt; ------------------------------------------------------------------------
<br>&gt;<br>&gt; _______________________________________________<br>&gt; Libraries mailing list<br>&gt; <a href="mailto:Libraries@haskell.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Libraries@haskell.org
</a><br>&gt; <a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.haskell.org/mailman/listinfo/libraries</a><br><br></blockquote></span></div></div><br>