From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Na Luke <NJLYF2011@hotmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Can you consider add official support for toybox?
Date: Mon, 26 Sep 2022 15:56:58 +0200 [thread overview]
Message-ID: <20220926155658.3f283176@windsurf> (raw)
In-Reply-To: <SJ0PR06MB68164DBA8D22BACEACC3B30ABA529@SJ0PR06MB6816.namprd06.prod.outlook.com>
Hello,
On Mon, 26 Sep 2022 13:46:25 +0000
Na Luke <NJLYF2011@hotmail.com> wrote:
> Toybox is a toolkit similar to busybox, it provides similar functions
> to busybox, and it is also used on the Android operating system.
>
> Its license agreement is relatively loose and can be used in some
> occasions where GPL is not applicable, so I think BuildRoot can
> consider adding support for toybox.
We would most likely welcome patches. I think there was a proposal a
long time ago, but it was complete enough. Packaging toybox is not that
simple. Of course, building it is easy. But then like Busybox, it
provides replacements/alternatives to a lot of tools, and we have
special handling in a number of packages for this. Would need to see
how that would work with Toybox.
So, yes, feasible, but not necessarily as trivial to do as it might
initially look like.
Best regards,
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
parent reply other threads:[~2022-09-26 13:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SJ0PR06MB68164DBA8D22BACEACC3B30ABA529@SJ0PR06MB6816.namprd06.prod.outlook.com>]
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=20220926155658.3f283176@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=NJLYF2011@hotmail.com \
--cc=buildroot@buildroot.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox