All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rsync: use system zlib and popt, also do not lose debug options
Date: Thu, 17 Oct 2013 18:18:26 +0200	[thread overview]
Message-ID: <52600DD2.1000502@mind.be> (raw)
In-Reply-To: <CAB++i-LMOO8owKF2V9eJdi_vX5W6LETLF-ywJ+x5bUMiGeoU+w@mail.gmail.com>

On 17/10/13 08:05, Denis Mingulov wrote:
> Hi,
>
>  > building only rsync before and after your patch, and although the
> binary becomes smaller with your patch, the overall filesystem becomes
> larger.
>
> Yes, in case of the only selected package it will be so. Due to overhead
> of shared library / not removed unused components.
> But for this particular case - you most probably have openssh (depends to
> zlib) or dropbear (depends to zlib if not 'small' version is selected
> separately) also already.
>
>  > I'd therefore propose to only use the system library if it is anyway
> selected.
>
> Sorry I am disagree, even without considering the security issue, just
> because zlib/popt for rsync are not optional libraries, they are
> mandatory, and will be compiled in any case.
> In the current buildroot .mk files such 'if' use case might be useful for
> optional components only, something like 'nice to have, will be supported
> if already present'. Otherwise there might be tens of components
> compiling its own 'zlib' version (tens different versions) - and the
> Buildroot user must somehow found FAQ or understand himself, that he must
> 'include zlib to the package manually' (zlib or tens of other libraries).
>
> Also it will be opposite to the current Buildroot configuration. In the
> latest master there are 9 packages with 'select BR2_PACKAGE_POPT'
> (cryptsetup, gptfdisk, libiscsi, librsync, logrotate, lttng-tools,
> oprofile, rpm, samba) and 50 packages with the same for zlib (of course
> not every one has its own zlib/popt).
>
> Might be, later it would be nice to have something like
> 'select_if_multiple' in Config files, to select other package if more
> than 1 component is selecting it, but it will do Configs more complex,
> and the use case is quite rare.

  Yeah, you're right.

  It was the "binary size is reduced by 25%" thing in your commit message 
that triggered me. That difference is probably irrelevant, because it 
hardly affects the overall filesystem size (rsync binary is relatively 
small).


  Regards,
  Arnout
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2013-10-17 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 11:40 [Buildroot] [PATCH] rsync: use system zlib and popt, also do not lose debug options Denis Mingulov
2013-10-16 12:26 ` Thomas Petazzoni
2013-10-16 13:13 ` [Buildroot] [PATCH v2] " Denis Mingulov
2013-10-17 16:19   ` Arnout Vandecappelle
2013-11-01 16:41   ` Thomas Petazzoni
2013-10-16 21:47 ` [Buildroot] [PATCH] " Arnout Vandecappelle
2013-10-17  6:05   ` Denis Mingulov
2013-10-17 16:18     ` Arnout Vandecappelle [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=52600DD2.1000502@mind.be \
    --to=arnout@mind.be \
    --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 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.