all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip McGrath <philip@philipmcgrath.com>
To: 59322@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#59322] [PATCH v2 4/4] etc: teams: Add chez.scm to Racket team's scope.
Date: Sat, 19 Nov 2022 18:52:39 -0500	[thread overview]
Message-ID: <111284438.nniJfEyVGO@bastet> (raw)
In-Reply-To: <106658bfff0dbda421cda6c45d76a4d3237d47e1.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]

On Saturday, November 19, 2022 2:54:55 AM EST Liliana Marie Prikler wrote:
> Am Freitag, dem 18.11.2022 um 14:33 -0500 schrieb Philip McGrath:
> > I could certainly imagine having a Chez team that doesn't necessarily
> > care about Racket. Likewise, in both languages, I imagine there could
> > be people  interested in packages that use the language but who
> > wouldn't necessarily be interested in the packaging of the compilers
> > and run-time systems themselves.
> > But, since no one else has signed on and I've made the majority of
> > changes to both files in the last two years, designing a more fine-
> > grained team structure seemed premature.
> 
> I can see where you're coming from, but my personal opinion is that
> merging these "two" teams now might discourage us from splitting them
> later.  In my humble opinion, adding a chez team with you as sole
> member wouldn't hurt for the time being.
> 

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?

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.)

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.

I just hope this need not delay the update to 8.7 any further.

-Philip

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-19 23:53 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 [this message]
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=111284438.nniJfEyVGO@bastet \
    --to=philip@philipmcgrath.com \
    --cc=59322@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.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 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.