HyperForum — Starting packaging haskell stack

Re: Starting packaging haskell stack

null@example.com (sagaracharya) — Sat, 18 Dec 2021 11:32:37 +0000

Very interesting. Very interesting. They're forcing to trust their binary! They should alternatively create something that can be compiled with some C compiler to remove that trust.

Re: Starting packaging haskell stack

null@example.com (throgh) — Fri, 17 Dec 2021 21:36:30 +0000

You need a version of fpc to compile fpc and therefore create the compiler. Afterwards you have a working package, you can create ghc and from that step by step all the rest of Haskell. It is a problematic way because you can download the binary package for fpc which is therefore resulting to be done for compilation the first package - for updates it would be done then with the new compiled package in the future going. So also the reasoning until now not integrating that!

Especially those packages you have mentioned in the first post are the reasoning we have no haskell for now, because the integration is not possible without binary releases and that is a real problem. Parabola GNU/Linux is importing packages from Arch Linux, so they have a starting point. We have this not and it would violate the concept for upcoming releases also. When you start from scratch you will be confronted with the essential problem of fpc in some comparable way: Your PKGBUILD would have to contain a binary-release of it to compile it.

Re: Starting packaging haskell stack

null@example.com (sagaracharya) — Fri, 17 Dec 2021 12:19:37 +0000

throgh wrote:

So you have to work up the whole stack from the ground.

What do you mean by that?

Is it something like the compiler written in C which can self-compile? I don't even know how self-compiling would work the 1st time unless the binary has been made by hand.

Re: Starting packaging haskell stack

null@example.com (throgh) — Fri, 17 Dec 2021 11:16:30 +0000

Own perspective: You need fpc and to build that you need fpc - again as binary-package. So you have to work up the whole stack from the ground. We have integrated fpc not for now!

Starting packaging haskell stack

null@example.com (sagaracharya) — Fri, 17 Dec 2021 10:43:49 +0000

Some genius has written the PKGBUILDs (at Parabola) for haskell stack

ghc-static depends on ghc
ghc depends on ghc-libs
ghc-libs depends on ghc-static (makedepend)

Where to start packaging haskell stack? Should I create PKGBUILD from scratch?