unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Philip McGrath <philip@philipmcgrath.com>,
	59322@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope.
Date: Sun, 20 Nov 2022 02:49:43 +0100	[thread overview]
Message-ID: <fd84f7be8e16495c06405b5af7700da41c0e6496.camel@gmail.com> (raw)
In-Reply-To: <111284438.nniJfEyVGO@bastet>

Am Samstag, dem 19.11.2022 um 18:52 -0500 schrieb Philip McGrath:
> [...]
> Is there a requirement that teams' scopes be disjoint? In other
> words, is there any reason "gnu/packages/chez.scm" shouldn't be in
> scope for both the racket team and a potential chez team?
Not necessarily, but I think exceptions should be well argued.  For
instance, it would make sense for a change in Emacs' build system to
reach both Emacs and core maintainers.  In practice however, core does
not have any build system in their scope, which strengthens my argument
for disjoint groups.

> Another factor that might be relevant: Matthew Flatt tells me he is
> actively working with the Chez Scheme maintainers to merge the two
> branches.  I'm not involved in these discussions myself: my
> understanding is that details are still being worked out, and I don't
> know what the time frame will be, but from what I'm told it's gone
> from "not in the foreseeable future" to "will happen".
> 
> (There's no plan to synchronize the release cycles, and Racket will
> continue to rely on unstable Chez system functions and to have the
> Chez version form part of its ABI, so we will likely continue to have
> a chez-scheme-for-racket package, but it should be a much simpler
> transformation to use a particular pre-release version.)
Depending on how well that goes, that'd be one headache less.  I'll be
cautiously optimistic and hope that Racket won't do another Zuo and
publish a subtree without release tags.

> After the merge, we should be able to bootstrap upstream Chez Scheme
> via Racket as we currently do with chez-scheme-for-racket, at which
> changes to Racket will also potentially impact Chez Scheme.
> 
> Personally, if there were more people involved, I'd organize it as
> teams for chez-and-racket-bootstrap, chez, and racket, as I'd
> initially tried to do in https://issues.guix.gnu.org/53878, but that
> especially seems like too much if they all consist of the same one
> person. If you still want a chez team, though, I guess I'm ok with
> that.
Three teams for two packages is definitely overkill.  I'd make it
either one or two, with the caveat that both of them being the same
should rest on a sound argument rather than a vague one.  If chez and
racket were interchangeable like different Common Lisp interpretations,
that'd be such an argument, or if there was a shared community not just
by virtue of bootstrapping.

> I just hope this need not delay the update to 8.7 any further.
Well, since CI already built everything and 1-3 LGTM, I went ahead and
pushed it, so you don't need to worry.

Cheers




  reply	other threads:[~2022-11-20  1:50 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
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 [this message]
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

  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=fd84f7be8e16495c06405b5af7700da41c0e6496.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=59322@debbugs.gnu.org \
    --cc=philip@philipmcgrath.com \
    --cc=zimon.toutoune@gmail.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 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).