From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Yocto Project <yocto@yoctoproject.org>,
Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH 2/3] busybox: Add setsid and cttyhack for tiny DISTRO_FEATURE
Date: Thu, 14 Jun 2012 10:41:04 +0100 [thread overview]
Message-ID: <1339666865.14857.39.camel@phil-desktop> (raw)
In-Reply-To: <3b44305edae36265295087fb5f31d22d660599b8.1339650859.git.dvhart@linux.intel.com>
On Wed, 2012-06-13 at 22:19 -0700, Darren Hart wrote:
> diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
> index 5b83d32..d07ba7e 100644
> --- a/meta/recipes-core/busybox/busybox.inc
> +++ b/meta/recipes-core/busybox/busybox.inc
> @@ -57,6 +57,8 @@ def features_to_busybox_settings(d):
> busybox_cfg('nls', distro_features, 'CONFIG_LOCALE_SUPPORT', cnf, rem)
> busybox_cfg('ipv4', distro_features, 'CONFIG_FEATURE_IFUPDOWN_IPV4', cnf, rem)
> busybox_cfg('ipv6', distro_features, 'CONFIG_FEATURE_IFUPDOWN_IPV6', cnf, rem)
> + busybox_cfg('tiny', distro_features, 'CONFIG_SETSID', cnf, rem)
> + busybox_cfg('tiny', distro_features, 'CONFIG_CTTYHACK', cnf, rem)
> return "\n".join(cnf), "\n".join(rem)
>
> # X, Y = ${@features_to_uclibc_settings(d)}
What exactly is the mission of the "tiny" DISTRO_FEATURE? It doesn't
seem very wholesome for it to be enabling a random grab-bag of bits in
busybox (or anywhere else).
If poky-tiny wants those features enabled then it can, and should, ship
its own configuration for busybox which turns them on. I think that
would be better than further proliferation of switches in oe-core.
p.
next prev parent reply other threads:[~2012-06-14 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1339650859.git.dvhart@linux.intel.com>
2012-06-14 5:19 ` [PATCH 2/3] busybox: Add setsid and cttyhack for tiny DISTRO_FEATURE Darren Hart
2012-06-14 5:21 ` Darren Hart
2012-06-14 7:05 ` Khem Raj
2012-06-15 22:22 ` Darren Hart
2012-06-15 22:57 ` Darren Hart
2012-06-14 9:41 ` Phil Blundell [this message]
2012-06-14 13:55 ` Darren Hart
2012-06-14 14:26 ` Phil Blundell
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=1339666865.14857.39.camel@phil-desktop \
--to=philb@gnu.org \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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