all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Philip McGrath <philip@philipmcgrath.com>, 59322@debbugs.gnu.org
Subject: [bug#59322] [PATCH 1/2] gnu: racket: Update to 8.7.
Date: Thu, 17 Nov 2022 08:30:22 +0100	[thread overview]
Message-ID: <6e91dc3c98d28fb4332a1b0109b23088b76b69f6.camel@ist.tugraz.at> (raw)
In-Reply-To: <4572a52575c06039b7fc91672e18bc1aebe951eb.1668634501.git.philip@philipmcgrath.com>

Am Mittwoch, dem 16.11.2022 um 16:39 -0500 schrieb Philip McGrath:
> Also, update 'chez-scheme-for-racket' to 9.5.9.8.
> 
> * gnu/packages/patches/racket-backport-8.6-cross-install.patch,
> gnu/packages/patches/racket-backport-8.6-docindex-write.patch,
> gnu/packages/patches/racket-backport-8.6-hurd.patch,
> gnu/packages/patches/racket-backport-8.6-zuo.patch: Remove patches.
Okay.
> * gnu/packages/patches/racket-backport-8.7-pkg-strip.patch: New
> patch.
The patch LGTM.
> * gnu/local.mk (dist_patch_DATA): Update accordingly.
This update seems non-complete – where the other backports previously
missing from our dist_patch_DATA?
> * gnu/packages/racket.scm (%racket-origin)[patches]: Likewise.
> (%racket-version): Update to 8.7.
> (racket)[inputs]: Add 'scheme-doc' source package from '%racket-
> origin'.
> (racket)[inputs]<compatibility, db, deinprogramm, draw, drracket,
> eopl,
> errortrace, gui, htdp, mzscheme, parser-tools, pict, plai, plot,
> r6rs,
> redex, scribble, slideshow, snip, typed-racket, srfi, string-
> constants>:
Use proper ChangeLog formatting, i.e. <compatibility,... drracket>
<eopl, errortrace, ...plot>
...
Pardon the potential off-by-one error due to the added quote columns.
> Update checksums.
> * gnu/packages/chez.scm (target-chez-arch): Support riscv64-linux-
> gnu.
> (%chez-features-table): Likewise.
> (chez-scheme-for-racket): Update to 9.5.9.8.
> [arguments]: Enable tests.
> [description]: Update.
> (chez-scheme-for-racket-bootstrap-bootfiles)[arguments]: Update path
> to
> 'rktboot'.
I suggest splitting this into two or three commits, where
(1. Update Chez scheme)
2. Update Racket with all the patches and checksums.
3. Update feature tables.

IIRC 1 and 2 share the definition of Racket origin, so it might not be
possible to split them, but it is definitely not necessary to enable
further arches that hitherto didn't work "in one go".


Cheers




  reply	other threads:[~2022-11-17  7:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 21:36 [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Philip McGrath
2022-11-16 21:39 ` [bug#59322] [PATCH 1/2] " Philip McGrath
2022-11-17  7:30   ` Liliana Marie Prikler [this message]
2022-11-18  0:45   ` [bug#59322] [PATCH v2 0/4] " Philip McGrath
2022-11-18  0:45     ` [bug#59322] [PATCH v2 1/4] " Philip McGrath
2022-11-18  0:45     ` [bug#59322] [PATCH v2 2/4] gnu: chez-scheme-for-racket: Support riscv64 Philip McGrath
2022-11-18  0:45     ` [bug#59322] [PATCH v2 3/4] gnu: racket-vm-cs: Avoid duplicate work Philip McGrath
2022-11-18  0:45     ` [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope Philip McGrath
2022-11-18  7:01       ` Liliana Marie Prikler
2022-11-18  8:26         ` zimoun
2022-11-18 19:23           ` Liliana Marie Prikler
2022-11-18 19:33           ` Philip McGrath
2022-11-19  7:54             ` Liliana Marie Prikler
2022-11-19 23:52               ` Philip McGrath
2022-11-20  1:49                 ` Liliana Marie Prikler
2022-11-23 18:44                 ` [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Ludovic Courtès
2022-11-21 16:50               ` [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope zimoun
2022-12-01 21:08       ` bug#59322: [PATCH 0/2] gnu: racket: Update to 8.7 Ludovic Courtès
2022-11-16 21:39 ` [bug#59322] [PATCH 2/2] gnu: racket-vm-cs: Avoid duplicate work Philip McGrath
2022-12-04 13:25 ` [bug#59322] [PATCH 0/2] gnu: racket: Update to 8.7 Enrico Schwass via Guix-patches via

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

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

  git send-email \
    --in-reply-to=6e91dc3c98d28fb4332a1b0109b23088b76b69f6.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=59322@debbugs.gnu.org \
    --cc=philip@philipmcgrath.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.