unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Cc: Lars-Dominik Braun <lars@6xq.net>,
	Alice BRENON <alice.brenon@ens-lyon.fr>,
	Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Core-updates after the staging merge
Date: Mon, 17 Apr 2023 14:19:43 +0200	[thread overview]
Message-ID: <87r0siem5c.fsf@gmail.com> (raw)
In-Reply-To: <ZD0X50bqPuyDSo8k@jurong>

Hi,

On lun., 17 avril 2023 at 11:56, Andreas Enge <andreas@enge.fr> wrote:
> Am Mon, Apr 17, 2023 at 11:03:25AM +0200 schrieb Andreas Enge:
>> - ghc is taking a long time...
>
> Actually ghc@9.0 fails its tests, which are written in Python (it looks
> like ".abc" needs to be added to collections); but since it is not needed
> for bootstrapping any more, maybe we could drop it?

Well, the current Haskell bootstrap chain is:

   7.8.4
-> 7.10.3
-> 8.0.2
-> 8.4.4
-> 8.6.5
-> 8.8.4
-> 8.10.7
-> 9.0.2; 9.2.5
-> 9.4.4 (next)

and instead we could try this shorter one:

   7.8.4
-> 8.0.2 (needs >= 7.10)
-> 8.4.4 (needs >= 8.0)
-> 8.8.4 (needs >= 8.4)
-> 9.2.5 (needs >= 8.6)

WDYT?  If no objection, I will give a try.



Moreover, the recipe for GHC looks like:

--8<---------------cut here---------------start------------->8---
(define-public ghc-9.0
  (package
    (inherit ghc-8.10)
    (name "ghc")
    (version "9.0.2")
    (source (origin
              (method url-fetch)
              (uri (string-append "https://www.haskell.org/ghc/dist/" version
                                  "/ghc-" version "-src.tar.xz"))
              (sha256
               (base32
                "15wii8can2r3dcl6jjmd50h2jvn7rlmn05zb74d2scj6cfwl43hl"))))
    (native-inputs
     `(;; GHC 9.0.2 must be built with GHC >= 8.8
       ("ghc-bootstrap" ,ghc-8.10)
       ("ghc-testsuite"
        ,(origin
           (method url-fetch)
           (uri (string-append
                  "https://www.haskell.org/ghc/dist/"
                  version "/ghc-" version "-testsuite.tar.xz"))
           (sha256
            (base32
             "1m5fzhr4gjn9ni8gxx7ag3fkbw1rspjzgv39mnfb0nkm5mw70v3s"))))
       ,@(filter (match-lambda
                   (("ghc-bootstrap" . _) #f)
                   (("ghc-testsuite" . _) #f)
                   (_ #t))
                 (package-native-inputs ghc-8.10))))
    (native-search-paths
     (list (search-path-specification
            (variable "GHC_PACKAGE_PATH")
            (files (list (string-append "lib/ghc-" version)))
            (file-pattern ".*\\.conf\\.d$")
            (file-type 'directory))))))
--8<---------------cut here---------------end--------------->8---

and it is similar for ’ghc-8.10’ and other, well something like:

    (native-inputs
     `(
       ("ghc-bootstrap" ,ghc-x.y)
       ("ghc-testsuite"
        ,(origin
           (method url-fetch)
           (uri (string-append
                  "https://www.haskell.org/ghc/dist/"
                  version "/ghc-" version "-testsuite.tar.xz"))

where ghc-x.y is a full GHC containing the complete testsuite.  I
propose here to replace by ’ghc-x.y/bootstrap’ where the tests are
turned off for this ghc-x.y/bootstrap.  We would not have to wait hours
and hours… Hum, I do not know if it is a good idea. :-)

I mean I propose to have both: ghc-x.y (with tests) and
ghc.x.y/bootstrap (without tests), it would ease the maintenance of the
Haskell ecosystem on several architectures.  WDYT?

Cheers,
simon



  reply	other threads:[~2023-04-17 12:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57   ` Andreas Enge
2023-04-17  8:06     ` Andreas Enge
2023-04-17  8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17  8:33   ` Andreas Enge
2023-04-17  9:03 ` Andreas Enge
2023-04-17  9:56   ` Andreas Enge
2023-04-17 12:19     ` Simon Tournier [this message]
2023-04-17 12:38       ` Andreas Enge
2023-04-17 12:57         ` Simon Tournier
2023-04-17 14:12       ` Lars-Dominik Braun
2023-04-17 17:47         ` Simon Tournier
2023-04-17 18:07           ` Andreas Enge
2023-04-17 19:01             ` Lars-Dominik Braun
2023-04-18 17:16               ` Andreas Enge
2023-04-21 18:29                 ` Lars-Dominik Braun
2023-04-17 12:57   ` Andreas Enge
2023-04-17 18:03   ` Maxim Cournoyer
2023-04-17 18:08     ` Andreas Enge
2023-04-18  5:04   ` John Kehayias
2023-04-18 17:38     ` Andreas Enge
2023-04-19 10:48   ` Latest news on core-updates Andreas Enge
2023-04-19 10:58     ` Christopher Baines
2023-04-19 12:41       ` Andreas Enge
2023-04-21  7:58         ` Andreas Enge
2023-04-21 13:01           ` Maxim Cournoyer
2023-04-20 13:56       ` Christopher Baines
2023-04-20 18:09         ` Andreas Enge
2023-04-21  8:20     ` Simon Tournier
2023-04-21  8:47       ` Andreas Enge
2023-04-21 11:31         ` Simon Tournier
2023-04-21 16:12     ` Katherine Cox-Buday
2023-04-21 16:12       ` Katherine Cox-Buday
2023-04-21 17:04       ` reza.housseini
2023-04-23  7:17         ` Andreas Enge
  -- strict thread matches above, loose matches on Subject: below --
2023-04-18  5:11 Core-updates after the staging merge John Kehayias

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0siem5c.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=alice.brenon@ens-lyon.fr \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).