On May 07, 2013 23:50, Matthias Kilian wrote: > Spoiler: I'm not talking about Haskell but about ghc here.
You mean keeping hugs and remove everything else? Because I don't see how hugs could build all the packages that make use of haskell2010 and all the ghc-extensions. The utrecht compiler isn't an option as well, because it needs ghc to bootstrap and even then doesn't support all ghc-extensions. To lower the impact of ghc we could remove all hs-ports that don't need patching and work out of the box with cabal. Or we could unhook all hs-ports and only keep the haskell-stuff hooked, that people need to build their desired hs-ports. If something breaks, it would be their problem to rebuild the hs-ports that would otherwise get a bump. I hope we can find a solution without removing ghc because that would force me to switch to another OS entirely :( (starting my thesis next week using haskell) > > I'd like to remove lang/ghc from the ports tree, because it's fucked > up beyond repair: > > - configure runs ghc-pwd (instead of just pwd) to determine the current > working directory. ghc-pwd is a program written in Haskell. In the > past, when ghc-pwd appeared, configure first compiled that ghc-pwd > program, which wouldn't work unless you already have a working > Haskell compiler installed. > > - after replacing all occurrences of ghc-pwd by /bin/pwd, the build > fails because it runs ghc-stage2 from the bootstrapper. (Note > that binaries for ghc-pwd as well as ghc-stage2 and much more are > included in the ghc sources and/or the bootstrapper for this > purpose). > > - bootstrapping without a pre-installed ghc still doesn't work, and > upstream doesn't careA > > - the ghc compiler is not deterministic, because function names (in > hs-libraries) depend on what's already built. So if you start a > build of ghc, interrupt it and restart it, you may end up with binary > incompatible libraries to an uninterrupted build. This is also the > reason for all those package bumps we do on hs-* ports. > > - with every new major ghc release, interfaces break. For example, last > summer I had to fix various "Num doesn't imply EQ" issues as > well as a lot of general typesystem issues. Imagine annual changes > to the C programming language that require not only recompiliton > but rewrites! > > So let's get rid of this crap. > > Ciao, > Kili >
