Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lvm2: replace !BR2_PACKAGE_LVM2_DMSETUP_ONLY by BR2_PACKAGE_LVM2_FULL_SUITE
Date: Mon, 25 Nov 2013 16:39:27 +0100	[thread overview]
Message-ID: <52936F2F.8040108@mind.be> (raw)
In-Reply-To: <52936E30.1000208@mind.be>

On 25/11/13 16:35, Arnout Vandecappelle wrote:
> On 25/11/13 16:10, Thomas De Schampheleire wrote:
>> On Mon, Nov 25, 2013 at 12:02 PM, Arnout Vandecappelle <arnout@mind.be>
>> wrote:
[snip]
>>
>> How 'large' is this application library? In this particular
>> configuration it is 810K (liblvm2app.so). Is it acceptable to include
>> it always in the 'full suite' (and thus remove the option
>> BR2_PACKAGE_LVM2_APP_LIBRARY)?
>
>   To help answer that question, on my x86_64 glibc build:
>
> 3.0M    /tmp/lvm2-app-library
> 2.1M    /tmp/lvm2-full-suite
> 472K    /tmp/lvm2-minimal

  Sorry, I forgot to strip and remove the redundant files. It should be:

2.5M    /tmp/lvm2-app-library
1.6M    /tmp/lvm2-full-suite
396K    /tmp/lvm2-minimal


  Conclusion remains the same, though.

>
>
>   So the app library adds another 40% to the package size. I guess that's
> significant enough not to remove the existing option. Especially because
> the only reason is that we can't find a better name for it :-)
>
>   My original name was "install all binaries", but I found that less
> descriptive than "full suite". Maybe "install all LVM2 programs"?
>
>   I could also copy the full list (which is in the .mk file) to the help
> text.
>
>   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-11-25 15:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-22 Thomas Petazzoni
2013-11-23 13:11 ` Thomas De Schampheleire
2013-11-23 15:09   ` Thomas De Schampheleire
2013-11-23 17:37     ` Thomas Petazzoni
2013-11-23 23:50       ` [Buildroot] [PATCH] lvm2: replace !BR2_PACKAGE_LVM2_DMSETUP_ONLY by BR2_PACKAGE_LVM2_FULL_SUITE Arnout Vandecappelle
2013-11-25  9:46         ` Thomas De Schampheleire
2013-11-25 11:02           ` Arnout Vandecappelle
2013-11-25 15:10             ` Thomas De Schampheleire
2013-11-25 15:35               ` Arnout Vandecappelle
2013-11-25 15:39                 ` Arnout Vandecappelle [this message]
2013-11-25 15:51                 ` Thomas De Schampheleire
2013-11-25 16:06                   ` Arnout Vandecappelle
2013-11-25 21:21             ` Thomas De Schampheleire
2013-11-28  7:13               ` Arnout Vandecappelle
2013-11-28 10:54                 ` Thomas De Schampheleire
2013-11-23 17:26   ` [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-22 Thomas Petazzoni
2013-11-25  9:26     ` Thomas De Schampheleire
2013-11-25  9:35       ` Thomas Petazzoni
2013-11-23 20:17   ` Baruch Siach
2013-11-25  9:25     ` Thomas De Schampheleire
2013-11-23 20:38 ` Romain Naour
2013-11-23 21:22   ` Yann E. MORIN
2013-11-23 21:34     ` Yann E. MORIN
2013-11-23 23:15   ` Yann E. MORIN

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=52936F2F.8040108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox