From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Philip McGrath <philip@philipmcgrath.com>, 47153@debbugs.gnu.org
Subject: [bug#47153] [PATCH] gnu: chez-scheme: simplify packaging
Date: Mon, 15 Mar 2021 23:21:28 +0100 [thread overview]
Message-ID: <9581850ed011d311db0388fcda41f8fbcd479730.camel@student.tugraz.at> (raw)
In-Reply-To: <ae6c7828-1e40-10fb-7a0f-b279989f416e@philipmcgrath.com>
Am Montag, den 15.03.2021, 17:53 -0400 schrieb Philip McGrath:
> Hi,
>
> On 3/15/21 2:28 PM, Leo Prikler wrote:
> > Then you should separate this into more than one patch.
>
> Ok, I've split this into three patches and kept nanopass and stex as
> origins. Is it preferred to send them here or to start a new thread?
The preferred way is to use `git send-email --reroll-count=N` (in this
case N=2, afterwards counting up). I would also ask you to do a
rebasing pull before sending emails and perhaps fix up some whitespace
issues. v1 failed to apply on cbaines' patchwork[1] with the following
(see also [2]):
error: patch failed: gnu/local.mk:879
error: gnu/local.mk: patch does not apply
> > > - I think the right thing would be to make chez-stex a
> > > public package, instead of the "stex" output of the chez-scheme
> > > package, but there are some bootstrapping issues I'll discuss
> > > below.
> > I agree. You can use the origin as an input to chez, like we've
> > done
> > before, then use the already built chez to compile stex into chez-
> > stex.
> > I don't think the latter half needs to be done right now, though,
> > you
> > can delay that until you feel more experienced in packaging.
>
> I think I understand (most of) how to do this
That's great!
> I think I'll put it off for now and see how it interacts with my
> Racket plans. Maybe there will be a more elegant bootstrapping
> solution.
Indeed, simpler patch sets are much appreciated.
Regards,
Leo
[1] https://patches.guix-patches.cbaines.net
[2] https://laminar.cbaines.net/jobs/patchwork-test-series/5359
next prev parent reply other threads:[~2021-03-15 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 8:42 [bug#47153] [PATCH] gnu: chez-scheme: simplify packaging Philip McGrath
2021-03-15 10:32 ` Leo Prikler
2021-03-15 18:03 ` Philip McGrath
2021-03-15 18:28 ` Leo Prikler
2021-03-15 21:53 ` Philip McGrath
2021-03-15 22:21 ` Leo Prikler [this message]
2021-03-15 22:53 ` [bug#47153] [PATCH v2 1/3] gnu: chez-scheme: Update nanopass to 1.9.2 Philip McGrath
2021-03-15 22:53 ` [bug#47153] [PATCH v2 2/3] gnu: chez-scheme: Update stex Philip McGrath
2021-03-15 22:53 ` [bug#47153] [PATCH v2 3/3] gnu: chez-scheme: simplify packaging Philip McGrath
2021-03-16 7:37 ` [bug#47153] [PATCH v2] gnu: chez-scheme: Update nanopass to 1.9.2 Leo Prikler
2021-03-16 20:19 ` Philip McGrath
2021-03-16 21:09 ` Leo Prikler
2021-03-19 18:24 ` [bug#47153] [PATCH v3 1/3] " Philip McGrath
2021-03-19 18:24 ` [bug#47153] [PATCH v3 2/3] gnu: chez-scheme: Update stex Philip McGrath
2021-03-19 18:24 ` [bug#47153] [PATCH v3 3/3] gnu: chez-scheme: simplify packaging Philip McGrath
2021-04-05 10:02 ` [bug#47153] [PATCH] " Ludovic Courtès
2021-04-05 14:20 ` bug#47153: " Leo Prikler
2021-03-20 16:06 ` [bug#47153] [PATCH v2] gnu: chez-scheme: Update nanopass to 1.9.2 Philip McGrath
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=9581850ed011d311db0388fcda41f8fbcd479730.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=47153@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 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).