Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] coreutils: allow selection of installed programs
Date: Wed, 24 Feb 2016 22:48:32 +0100	[thread overview]
Message-ID: <20160224214832.GA3449@free.fr> (raw)
In-Reply-To: <56CE1E61.7000008@zacarias.com.ar>

Gustavo, Romain, All,

On 2016-02-24 18:19 -0300, Gustavo Zacarias spake thusly:
> On 22/02/16 05:40, Romain Izard wrote:
> 
> >My issue is that I'm updating an existing system, and the application
> >has expensive scripts that rely on the behaviour of coreutils regarding
> >some options that busybox does not have. As I cannot easily change those
> >scripts, my goal is to try to provide the same services with an updated
> >rootfs. To keep everything (including wifi, bluetooth, glib and a lot
> >more) in less 10 MiB as it did in the past, removing even 300 KiB from
> >coreutils is a step in the right direction. And I though it was a better
> >if is was done in a clean way, instead of the ad-hoc patches I had in
> >the previous generation
> >
> >But if you think buildroot does not need it, I won't insist.
> >
> >Best regards,
> 
> Hi Romain.
> How about adding a more lightweight option to the coreutils package to
> disable the single-binary mode?

Yes, that is a great ides, maybe a choice like:

    choice
        bool "Single-binary mode"
        default BR2_PKG_COREUTILS_SINGLE_SYMLINKS

    config BR2_PKG_COREUTILS_SINGLE_NONE
        bool "none"

    config BR2_PKG_COREUTILS_SINGLE_SYMLINKS
        bool "symlinks"

    config BR2_PKG_COREUTILS_SINGLE_SHEBANGS
        bool "shebangs"

    endchoice

And the corresponding code in the .mk file, of course.

Regards,
Yann E. MORIN.

> That way if all you want is 1-2 binaries you can purge the rest from a
> post-build script to save space, if you want more then single-binary mode
> makes sense to kill code duplication.
> Regards.
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-02-24 21:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 11:14 [Buildroot] [PATCH v1 1/1] coreutils: allow selection of installed programs Romain Izard
2016-02-03 16:34 ` Thomas Petazzoni
2016-02-03 17:13   ` Romain Izard
2016-02-12 13:48     ` Romain Izard
2016-02-21 22:09 ` Peter Korsgaard
2016-02-22  8:40   ` Romain Izard
2016-02-24 21:19     ` Gustavo Zacarias
2016-02-24 21:48       ` Yann E. MORIN [this message]
2016-02-24 21:58         ` Peter Korsgaard
2016-02-24 22:19           ` Yann E. MORIN
2016-02-25 10:54             ` Romain Izard
2016-02-25 10:59               ` Peter Korsgaard
2016-02-25 19:30                 ` Yann E. MORIN
2016-02-25 22:31               ` Arnout Vandecappelle
2016-02-26  8:26                 ` Romain Izard

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=20160224214832.GA3449@free.fr \
    --to=yann.morin.1998@free.fr \
    --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