From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11836] Embedded Shell Scripts in BusyBox
Date: Fri, 03 May 2019 15:09:04 +0000 [thread overview]
Message-ID: <bug-11836-163-hhA10Latug@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11836-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11836
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Max, All,
> It would be great to be able to use [embedded scripts]
What is the advantage over having the scripts installed in /bin or /usr/bin
instead? If you are concerned about space that much that you want to take
advantage of busybox' compression of the scripts, you would anyway consider
a compressed filesystem like squashfs anyway, so the space gain would
probably be ridiculous.
> there is no configuration option in buildroot [for that]
Indeed no, but it should not be overly complex to add. Yet, I'd like to
see a good explanations why that would be better than to have the scripts
in the filesystem instead.
Regards,
Yann E. MORIN.
PS. Yes, support for embedded scripts is enabled in a default build, but
that's an accident: our busybox .config was created before embedded scripts
were a thing, so they are not explicitly disabled in our .config, and since
the default for them in busybox is 'y', we end up with a buysbox that has
support for embedded script (but no such script).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-05-03 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 14:43 [Buildroot] [Bug 11836] New: Embedded Shell Scripts in BusyBox bugzilla at busybox.net
2019-05-03 15:09 ` bugzilla at busybox.net [this message]
2019-05-03 18:30 ` [Buildroot] [Bug 11836] " bugzilla at busybox.net
2019-05-03 18:44 ` bugzilla at busybox.net
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=bug-11836-163-hhA10Latug@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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