Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Sven Panne
On Thursday 15 March 2007 21:28, Ian Lynagh wrote: On Thu, Mar 15, 2007 at 07:46:09PM +0100, Sven Panne wrote: BTW, the toplevel directory of darcs.haskell.org needs some serious cleanup, There are plans[0] to get a community server where anyone can come along and get a project hosted in

Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Sven Panne
On Thursday 15 March 2007 21:34, Ian Lynagh wrote: hsc2hs gives different output on different platforms, so anyone building from source needs it, not just those building from darcs. I came to the same conclusion this morning while standing under the shower... :-) So things are quite different

Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Malcolm Wallace
Sven Panne [EMAIL PROTECTED] wrote: OK, now I remember. :-) Hmmm, that seems to indicate that splitting off at least cpphs from the Hugs/nhc98 distributions is the right way. And because of a similar reasoning, hsc2hs should not be distributed with nhc98. But the very reason that cpphs and

Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Malcolm Wallace
Sven Panne [EMAIL PROTECTED] wrote: GHC/Hugs/nhc should fetch these tools via their darcs-all script and use it for bootstrapping themselves, At least nhc98 already does this. :-) but they should *not* install these tools along with the compiler/interpreter in question. Well, perhaps

[nightly] 16-Mar-2007 build of of 6.6 branch on i386-unknown-mingw32 (bling)

2007-03-16 Thread sof
From: GHC Build Reports [EMAIL PROTECTED] To: cvs-ghc@haskell.org Subject: [nightly] 16-Mar-2007 build of of 6.6 branch on i386-unknown-mingw32 (bling) Build description = of 6.6 branch on i386-unknown-mingw32 (bling) Build location= /fptools/builds/STABLE Build config file =

patch applied (ghc): Comment out debug traces

2007-03-16 Thread Simon Peyton Jones
Fri Mar 16 06:38:22 PDT 2007 [EMAIL PROTECTED] * Comment out debug traces M ./compiler/iface/IfaceEnv.lhs -2 +2 M ./compiler/iface/LoadIface.lhs -1 +1 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org

patch applied (ghc): Refactor TcRnDriver, and check exports on hi-boot files

2007-03-16 Thread Simon Peyton Jones
Fri Mar 16 06:38:50 PDT 2007 [EMAIL PROTECTED] * Refactor TcRnDriver, and check exports on hi-boot files This patch refactors TcRnDriver to make the top-level structure easier to understand. The change was driven by Trac #924, and this patch fixes that bug. When comparing a

Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Ian Lynagh
On Fri, Mar 16, 2007 at 12:18:21PM +0100, Sven Panne wrote: We *do not* install hsc2hs anymore, and make it a standalone project distributed separately. Same for cpphs. The only issue I see is that Cabal calls hsc2hs when necessary, but alex and happy are already in the that situation.

Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Sven Panne
On Friday 16 March 2007 15:45, Ian Lynagh wrote: The only issue I see is that Cabal calls hsc2hs when necessary, but alex and happy are already in the that situation. Unfortunately packages can't depend on tools, they just fail when asked to build. Perhaps there should be a cabal Tools: field

Re: patch applied (ghc): Use update-alternatives for handling generic tool names

2007-03-16 Thread Ian Lynagh
On Fri, Mar 16, 2007 at 12:12:49PM +, Malcolm Wallace wrote: Sven Panne [EMAIL PROTECTED] wrote: but they should *not* install these tools along with the compiler/interpreter in question. However, nhc98 won't mind in the slightest if somebody else installs cpphs as well, or over