From: Darren Hart <dvhart@linux.intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] busybox: Include setsid and cttyhack in defconfig
Date: Sat, 16 Jun 2012 09:38:40 -0700 [thread overview]
Message-ID: <4FDCB690.8090004@linux.intel.com> (raw)
In-Reply-To: <1339863500.3339.150.camel@x121e.pbcl.net>
On 06/16/2012 09:18 AM, Phil Blundell wrote:
> On Fri, 2012-06-15 at 15:56 -0700, Darren Hart wrote:
>> So the delta for including SETSID and CTTYHACK is 2560 bytes.
>
> Personally I am still not in favour of adding this to the default
> configuration. I appreciate that it's "only" 2.5k in this case, but
> every time we make a change like this the binary gets a little bit
> bigger and, over time, it does add up. This sort of gradual bloat is
> quite insidious and difficult to combat after the fact.
>
> So, I continue to think that poky-tiny should just provide its own
> busybox configuration and turn on the options that it wants just like
> other DISTROs do. No doubt there are some things currently included in
> the oe-core defaults that poky-tiny doesn't need, so you would probably
> get a smaller binary that way as well.
You are correct that poky-tiny would benefit from a smaller config. My
original intent was to update the busybox recipe to use the new
merge-config.sh that we pushed to the upstream Linux kernel (which
should work with busybox as it uses the same config mechanism). This
would allow us to maintain a base busybox config with a several config
fragments that can be easily added via DISTRO_FEATURES rather than the
complicated hack that is in busybox now for handling DISTRO_FEATURES. I
prefer this approach as it reduces (if not eliminates) the need for the
proliferation of busybox.bbappend files.
However, this is a larger project and my immediate goal is to get
poky-tiny into better shape in terms of the initial experience. This is
why I originally implemented it as a "tiny" DISTRO_FEATURE as that would
migrate naturally to the config fragment approach. You and others
objected to that approach, and I do understand not wanting to complicate
the DISTRO_FEATURE logic further.
With the above goal in mind, can you accept either of my proposed
patches as an interim solution? Either as an added tiny DISTRO_FEATURE
or as a simple addition to the defconfig? I do believe these two
features are useful beyond poky-tiny.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-16 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:39 [PATCH 0/1] busybox: Include setsid and cttyhack in defconfig Darren Hart
2012-06-15 22:40 ` [PATCH 1/1] " Darren Hart
2012-06-15 22:56 ` Darren Hart
2012-06-16 16:18 ` Phil Blundell
2012-06-16 16:38 ` Darren Hart [this message]
2012-06-16 17:47 ` Khem Raj
2012-06-16 21:47 ` Darren Hart
2012-06-17 2:41 ` Koen Kooi
2012-06-17 21:14 ` Paul Eggleton
2012-06-17 21:55 ` Khem Raj
2012-06-18 5:00 ` Koen Kooi
2012-06-18 7:58 ` Paul Eggleton
2012-06-18 9:26 ` Koen Kooi
2012-06-18 10:43 ` Paul Eggleton
2012-06-18 11:35 ` Phil Blundell
2012-06-18 14:28 ` Darren Hart
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=4FDCB690.8090004@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.org \
/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