From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad via buildroot <buildroot@buildroot.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 4/4] package/janet-spork: new package
Date: Sat, 27 Dec 2025 23:11:14 +0100 [thread overview]
Message-ID: <20251227231114.72a279bc@windsurf> (raw)
In-Reply-To: <20251220173412.433583-4-francois.perrad@gadz.org>
Hello,
On Sat, 20 Dec 2025 18:34:12 +0100
Francois Perrad via buildroot <buildroot@buildroot.org> wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
What does this package actually provides? If I understand correctly,
janet-spork is like an utility library of some sort. What are you using
it for? For your own custom Janet-based application?
Are there some Janet-based applications that are available so that this
janet-package infrastructure can actually be used for something
_useful_ ?
But really aside from that the patch looks really good and clean.
Can you do a v2 adjusting the few comments on the rest of the series,
and providing a bit more background? Then we can go ahead and merge
this.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-12-27 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 17:34 [Buildroot] [PATCH 1/4] package/janet: add host variant Francois Perrad via buildroot
2025-12-20 17:34 ` [Buildroot] [PATCH 2/4] package/jmp: new host package Francois Perrad via buildroot
2025-12-27 22:05 ` Thomas Petazzoni via buildroot
2025-12-20 17:34 ` [Buildroot] [PATCH 3/4] package/janet: new infrastructure Francois Perrad via buildroot
2025-12-27 22:07 ` Thomas Petazzoni via buildroot
2025-12-20 17:34 ` [Buildroot] [PATCH 4/4] package/janet-spork: new package Francois Perrad via buildroot
2025-12-27 22:11 ` Thomas Petazzoni via buildroot [this message]
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=20251227231114.72a279bc@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=thomas.petazzoni@bootlin.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.
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.