Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 18:44:05 +0000	[thread overview]
Message-ID: <bug-11836-163-OLfw0lysjs@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
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Max, All,

> Beside the benefit of additional free space on the target filesystem (due
> to the compression of the scripts),

As I said: if you are really concerned about the size of the scripts that
you need them to be compressed, you will probably better benefit from a
compressed filesystem to begin with, like squashfs, which would compress
everything, from busybox itself, to the libraries it uses like libc et al.
to all the files on the systems, and not just the few scripts that are
embedded in the busybox binary.

Honestly, I doubt embedding the scripts in the busybox binary wins over
having a squashfs, but I'd like to see numbers.

> another advantage is that it is not necessary to take care about script
> file permissions (there is no need to set execute-permissions when the
> scripts are embedded into the BusyBox binary).

If you can't track the executable bit on your scripts, you have a big
problem in your tooling and/or process and/or build environment.

Again, I am not opposed to having support for embedded scripts, but I'd
like to see a *convincing* argument...

BTW, this is not a bug, but an enhancement request. We usually take new
features as patches sent to the mailing list, so I'm closing this bug.

Regards,
Yann E. MORIN.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2019-05-03 18:44 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 ` [Buildroot] [Bug 11836] " bugzilla at busybox.net
2019-05-03 18:30 ` bugzilla at busybox.net
2019-05-03 18:44 ` bugzilla at busybox.net [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=bug-11836-163-OLfw0lysjs@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