Received: from cogitri.dev (v2202108153511159606.happysrv.de [202.61.197.178]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 1D304780DD0 for <~alpine/devel@lists.alpinelinux.org>; Thu, 21 Oct 2021 13:27:18 +0000 (UTC) Date: Thu, 21 Oct 2021 15:27:13 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cogitri.dev; s=mail; t=1634822835; bh=0txqGH/hNvQiOIu1YNb7OvERUWaD6491jIn1+OKtXQE=; h=From:To:Cc:In-Reply-To:References:Subject; b=bWrhMUxh7vXrQN/iMmgqR1cK+UYCFNaa9kGmGmdlEtRQ/Mk45DC8bJKQYBBunhe0V 4Ac2w6zcbuK2K7zaBjtuWm9ogJ1Q8RP9aKTGEcHPhUQmJIuToudEgEw24FjtwfsNo0 eVLDsZTIEqP7EzGL2FHDQhLoNzV5PwqhZRY/xVD09fg1XN1oPTRxLCYUGi7L9l8XKu MdISE+QcK4/SSHx7hd7N6TXNtevtLEjiv9V+c8LypKNTRLFswvz4UlaWjQoXkZK9es OalDVb5g0njVh5AQT0ZkXl5feGRTnLqyOddHOnBc6D13IluHUD5uOFE3kl2Py3t8J8 iKeZFHXcEwCKg== From: Rasmus Thomsen To: Natanael Copa , Alpine development <~alpine/devel@lists.alpinelinux.org> Cc: Olliver Schinagl , Mitch Tishmack Message-ID: In-Reply-To: <20211021133615.32f08070@ncopa-desktop.lan> References: <20211021133615.32f08070@ncopa-desktop.lan> Subject: Re: Remove haskell compiler (ghc) from alpine Mime-Version: 1.0 Content-Type: multipart/signed; boundary="61716ab2_507ed7ab_2fa6"; protocol="application/pgp-signature" --61716ab2_507ed7ab_2fa6 Content-Type: multipart/alternative; boundary="61716ab1_3d1b58ba_2fa6" --61716ab1_3d1b58ba_2fa6 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, IMHO we can just drop those packages. Our ghc has been stale for some tim= e now and we don=E2=80=99t really have any core developers which care abo= ut it (I think). Additionally only a few packages need it so I don=E2=80=99= t really think it=E2=80=99s worth keeping it especially now that it block= s the release. Regards, Rasmus > On Thursday, Oct 21, 2021 at 1:36 PM, Natanael Copa wrote: > =23=23 TL;DR > > ghc is blocking the 3.15 release, so I wonder if we can remove > the following packages: > > - community/gch > - community/cabal > - community/shellcheck > - testing/pandoc > - testing/apostrophe > > =23=23 longer explanation > > Maintaining ghc and cabal packages requries significant amount > of time and skills. To my understanding, upstream recommends use ghcup > to install haskell, not the distro package. > > We use shellcheck in our CI but shellcheck is available from upstream > as a statically precompiled binary=5B1=5D which we can use for our infr= a. > > pandoc is also available as precompiled binary=5B2=5D. > > But those cannot be used as dependencies for other packages which means= > that we cannot provide a package for testing/apostrophe or > testing/py3-pypandoc. > > Would it be ok to remove those packages to save ourselves from > significant amount of maintenance work=3F > > Alternatively, are there anyone who have time and skills to take > maintenance for those=3F What needs to be done: > > - complete the update of ghc to 9.0.2 =5B3=5D: > - either revert back to system libffi (and add comment in libffi > package that special care is needed when upgrading libffi due to > ghc needing ghc to update) or solve how the bundled libffi is handled. > - find out how to update cabal. one of the following alternatives > needs to be done: > a) copy the way boostrap.sh from cabal 3.2.0.0 works (fetch and > build all the needed deps together with cabal-install itself). > b) figure out if/how we can use cabal's bootstrap.py=5B4=5D > c) find out how to use previous cabal to update cabal (another > circular dep) and investigate what the consequences of that is. > (any external dependencies will need special care when the are > upgraded). > d) create apk packages for the dependencies, similar to what arch > linux does=5B5=5D. eg package for uusi=5B6=5D, haskell-hashable=5B7=5D = etc. > - split out ghc-libs runtime libraries > > - rebuild everything using the ghc (shellcheck, pandoc, py3-pypandoc > etc) > > - figure out and document how to do the haskell-* packages in case > option d) was chosen above. Maybe also add support for haskell > packages in newapkbuild. > > - figure out how to bootstrap ghc and cabal for the remaining > architectures. At least aarch64. > > I have already spent way too many days on ghc and would prefer that > someone else takes over or that we remove it. > > =5B1=5D: https://github.com/koalaman/shellcheck/releases/tag/v0.7.2 > =5B2=5D: https://github.com/jgm/pandoc/releases/tag/2.14.2 > =5B3=5D: https://gitlab.alpinelinux.org/alpine/aports/-/merge=5Frequest= s/20134 > =5B4=5D: https://github.com/haskell/cabal/tree/master/bootstrap > =5B5=5D: https://github.com/archlinux/svntogit-community/blob/packages/= cabal-install/trunk/PKGBUILD > =5B6=5D: https://github.com/archlinux/svntogit-community/blob/packages/= uusi/trunk/PKGBUILD > =5B7=5D: https://github.com/archlinux/svntogit-community/blob/packages/= haskell-hashable/trunk/PKGBUILD --61716ab1_3d1b58ba_2fa6 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline <= meta name=3D=22viewport=22 content=3D=22width=3Ddevice-width, initial-sca= le=3D1.0, user-scalable=3Dno=22> 3D=22=22
Hi,

IMHO we can just dro= p those packages. Our ghc has been stale for some time now and we don=E2=80= =99t really have any core developers which care about it (I think). Addit= ionally only a few packages need it so I don=E2=80=99t really think it=E2= =80=99s worth keeping it especially now that it blocks the release.
=

Regards,

Rasmus
<= br>


<= div>On Thursday, Oct 21, 2021 at 1:36 PM, Natanael Copa <ncopa=40alpinelinux.org> wrote:<= br>
=23=23 TL;DR

ghc is blocking the 3.15 release, so I= wonder if we can remove
the following packages:

- community/gc= h
- community/cabal
- community/shellcheck
- testing/pandoc
-= testing/apostrophe

=23=23 longer explanation

Maintaining g= hc and cabal packages requries significant amount
of time and skills. = To my understanding, upstream recommends use ghcup
to install haskell,= not the distro package.

We use shellcheck in our CI but shellchec= k is available from upstream
as a statically precompiled binary=5B1=5D= which we can use for our infra.

pandoc is also available as preco= mpiled binary=5B2=5D.

But those cannot be used as dependencies for= other packages which means
that we cannot provide a package for testi= ng/apostrophe or
testing/py3-pypandoc.

Would it be ok to remove= those packages to save ourselves from
significant amount of maintenan= ce work=3F

Alternatively, are there anyone who have time and skill= s to take
maintenance for those=3F What needs to be done:

- com= plete the update of ghc to 9.0.2 =5B3=5D:
- either revert back to sys= tem libffi (and add comment in libffi
package that special care is ne= eded when upgrading libffi due to
ghc needing ghc to update) or solve= how the bundled libffi is handled.
- find out how to update cabal. o= ne of the following alternatives
needs to be done:
a) copy the wa= y boostrap.sh from cabal 3.2.0.0 works (fetch and
build all the neede= d deps together with cabal-install itself).
b) figure out if/how we c= an use cabal's bootstrap.py=5B4=5D
c) find out how to use previous ca= bal to update cabal (another
circular dep) and investigate what the c= onsequences of that is.
(any external dependencies will need special = care when the are
upgraded).
d) create apk packages for the depen= dencies, similar to what arch
linux does=5B5=5D. eg package for uusi=5B= 6=5D, haskell-hashable=5B7=5D etc.
- split out ghc-libs runtime libra= ries

- rebuild everything using the ghc (shellcheck, pandoc, py3-p= ypandoc
etc)

- figure out and document how to do the haskell-*= packages in case
option d) was chosen above. Maybe also add support = for haskell
packages in newapkbuild.

- figure out how to boots= trap ghc and cabal for the remaining
architectures. At least aarch64.=

I have already spent way too many days on ghc and would prefer th= at
someone else takes over or that we remove it.

=5B1=5D: https= ://github.com/koalaman/shellcheck/releases/tag/v0.7.2
=5B2=5D: https:/= /github.com/jgm/pandoc/releases/tag/2.14.2
=5B3=5D: https://gitlab.alp= inelinux.org/alpine/aports/-/merge=5Frequests/20134
=5B4=5D: https://g= ithub.com/haskell/cabal/tree/master/bootstrap
=5B5=5D: https://github.= com/archlinux/svntogit-community/blob/packages/cabal-install/trunk/PKGBUI= LD
=5B6=5D: https://github.com/archlinux/svntogit-community/blob/packa= ges/uusi/trunk/PKGBUILD
=5B7=5D: https://github.com/archlinux/svntogit= -community/blob/packages/haskell-hashable/trunk/PKGBUILD
=
--61716ab1_3d1b58ba_2fa6-- --61716ab2_507ed7ab_2fa6 Content-Type: application/pgp-signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: Canary PGP V3 iQI+BAABCgAoIRxSYXNtdXMgVGhvbXNlbiA8b3NzQGNvZ2l0cmkuZGV2PgUCYXFq sgAKCRARFSQVGBVOptR5D/90r220ZVvI9lKRIgQfbcHQZspHNouFlbT8WCnrUx5d fXt0JMNo8xosd8L77gAUlt39F61lFdiauyFrIZ7zJ/f1QXyUEDdh7VW1jkT8aPKc MhbR/J+UJYLXJwW78lRVoSEiJNzveuWAEzmy8GRZ3wqeoCtDMbIB1COo45z633tZ g6Z7PG1yhfctLAuHnVtFqE3ifThAi83nJFHE4ZzS3VvzruOhBxa14Ww1g2B1MGuK +p4c6vylw57QwsDAF7cD4mtOY0qiGIKECdjhb2DfA9OQnn2/0ILEX1XJIQui7tN6 MO47FmCmW85XkpWTCpeIiF4cZAH9VG315rbp/28H9Iy3U0YzigSuXzve/bg5d2lG JZInjJhnz06r0Sw1BLV+E5SQNJ6ZvyyyiaDNykDyBGoYt2unsRh4K4NgKaJj/NXv ohAh3kbZc/23UNIt1F2RXOrab9Qfq9Zn+sqp3K9lkTPYNy+dx8xXzoKUu4nrdx7k 1TqSqfAtpSm0q3V6SR9sXGPxfAWZNBC+PodcMrooMGmb2aLYkVdD0JdKYHYq8LIm /Iqxynz+5CMxUvwWQCRJlpxr/bqA5trjdSG4Wx9CNiz3VVXPmngApUMNS5rJD9mV GC4GuJbL/xz//qTdEVqdr+bA0Tr34wGj7rNUQyign9wmD2NqQXdM+Ou5YZO7zku+ 6g== =B6vf -----END PGP SIGNATURE----- --61716ab2_507ed7ab_2fa6--