Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#154 ghc for 14.0

closed
None
Normal
New
14.0
2013-04-06
2012-11-03
mimosa
No

Discussion

    • assigned_to: Frédéric Galusik
     
  • uploaded.

    ++

     
    • status: open --> closed
     
    • status: closed --> open
     
  • I'm sorry, it's my fault, I should have best checked it, I still don't understand how I missed that. Anyway, better late than ever ;) :

    1) All doc have to be moved to /usr/doc/$pkgname-$pkgver
    2) The cabal executable is missing.

    Cabal is a tool for users to locally install Haskell libs and apps.
    I found that miss when I try to install pandoc, so I re-check the pkg.
    http://johnmacfarlane.net/pandoc/installing.html

    ++

     
  • mimosa
    mimosa
    2012-12-03

    The docs are easy to fix - my bad. Regarding cabal, you need to install haskell-platform (available from slkbuilds.org) as it says in those instructions.
    I mean to make some more haskell packages, including haskell-platform, some time soon. ghc alone is not enough! But it does avoid the need for an ugly hack( without which the SlackBuild fails) and what can be a very long build.

    If this isn't too urgent (just the location of the docs), I would actually like to make some other changes to the ghc package. I have been talking to one of the Haskell devs and it seems the existing ghc SlackBuild provides a ghc ('Stage 0') that should really then be used to build two more versions ('Stage 1' and 'Stage 2'). There is then no need for any library trickery because everything is truly native. I didn't undertake this because the packaging cycle is coming to an end, the current version works perfectly well (and is at least superior to the SlackBuild), and a lot of testing would be involved to make sure the new version works with other Haskell stuff such as haskell-platform. Indeed it might make sense to provide newer versions of everything, in which case this would be a medium-sized project. I had it in mind to deliver it gradually under "submitted packages".

    Anyway, let me know what you think.

     
  • Ok for cabal, I will check haskell-platform, thanks.

    I trust you for making a better package ;)
    I think it's important to have a very good haskell env., as others languages too, if we want to attract more developpers who want to work on Slackware without losing time installing and configuring it.

    Else, that's not so urgent but if it will take you weeks to build a new one, it is maybe safer to do a quick fixed rebuild.

    ++

     
  • mimosa
    mimosa
    2012-12-03

    See here on the Haskell Platform:
    http://www.haskell.org/platform/
    Note that it needs to be installed on top of ghc (see Linux page).

    It would be nice to have everything included in the 14.0 repos. Actually making the improved ghc package won't take too long, but if it makes any of the SlackBuilds that depend on ghc fail, that will take longer - it would mean making new packages for everything. But that probably won't happen. I think it would be a reasonable aim to have both a kosher ghc and haskell-platform available as Salix packages. Can you give me, say, a couple of weeks?

     
  • Of course ;)

    ++

     
  • mimosa
    mimosa
    2012-12-04

    Does the package need to include the stage 0 compiler? The instructions for building ghc are "first get a working ghc from somewhere" then build it. That working ghc is the ghc that the current package provides.
    It doesn't really make too much difference to me in the sense that I have already done the work for stage 0. So the SLKBUILD will just be the old one with some more stuff added. It also won't affect the final binaries either way. But it does mean a much longer build and uploading two or three hundred more MB of source files, so if it isn't necessary to make a package that really does build from the ground up, it would be more convenient. I could include some comment lines in the SLKBUILD explaining where Stage 0 comes from, meaning anyone curious would still be able to reproduce the entire build process.

    What do you think?

     
  • I don't mind uploading more source files.
    The more important is that anyone can rebuild your pkg with the source, so, do what you feel better ;)

    ++

     
  • mimosa
    mimosa
    2012-12-14

    My new build fails a handful of the 3000-odd tests in the slimline test suite, but the documentation says any failure is unacceptable. However, the old build (in the Salix repos) fails roughly the same tests (depending on some tweaks).

    I have come round to the view that the package should just presume a GHC is already present - indeed, not only GHC, but a full working system, including Haskell Platform. That's how everyone else does it, and what the instructions say.

    Meanwhile, if I can't either fix the dodgy test results or confirm from GHC devs that they are insignificant, in a day or two I will upload an interim package the same as the old one but with docs in the right place. That will provide a GHC identical to the one from slackbuilds.org but without the long build (though it isn't a "build" as such, just a mammoth unpacking and repacking).

     
  • mimosa
    mimosa
    2012-12-17

    I have since established that the new build fails fewer tests than the existing bindist one (3 versus 13) and also that it's more or less normal: the comments in the Arch package for a more recent GHC, 7.6.1, mention a similar number of failures, some of them the very same ones, some associated with bug tickets. To put it another way, maybe the failures are a problem, but they are an upstream problem.

    Taking all that into consideration, I think this build can be adopted by Salix with confidence. I'm now rebuilding in a clean environment, and will also try my hand at a package for the Haskell Platform (as well as its dependency hscolour). If that works, anything else (such as XMonad) can be installed using Cabal.

     
  • Sorry, I missed that post :(
    Is it ok ?

    ++

     
  • mimosa
    mimosa
    2013-02-18

    On Mon, 18 Feb 2013, "Frédéric Galusik" wrote:

    Sorry, I missed that post :(
    Is it ok ?
    I haven't looked at these since then (and my clean packaging installs
    are long gone) but the change was just to move docs around. I gave up on
    making a true bootstrapped version - maybe by the time 15.0 comes round
    I will have learned how.

    So this should be fine!

     
  • Uploaded. (finally)

    ++

     
    • status: open --> closed