From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] busybox: picking IPv6 per default is not up to the package
Date: Wed, 9 Jun 2010 21:32:42 +0200 [thread overview]
Message-ID: <20100609193242.GR14941@mx.loc> (raw)
In-Reply-To: <1276111093.4424.21.camel@lenovo.internal.reciva.com>
On Wed, Jun 09, 2010 at 08:18:13PM +0100, Phil Blundell wrote:
>On Wed, 2010-06-09 at 20:52 +0200, Bernhard Reutner-Fischer wrote:
>> On Wed, Jun 09, 2010 at 07:44:58PM +0100, Phil Blundell wrote:
>> >On Wed, 2010-06-09 at 19:10 +0200, Bernhard Reutner-Fischer wrote:
>> >> diff --git a/recipes/busybox/busybox-1.15.3/micro/defconfig b/recipes/busybox/busybox-1.15.3/micro/defconfig
>> >> index 8431d19..f6eaa6d 100644
>> >> --- a/recipes/busybox/busybox-1.15.3/micro/defconfig
>> >> +++ b/recipes/busybox/busybox-1.15.3/micro/defconfig
>> >> @@ -608,7 +608,7 @@ CONFIG_TIME=y
>> >> #
>> >> # Networking Utilities
>> >> #
>> >> -CONFIG_FEATURE_IPV6=y
>> >> +# CONFIG_FEATURE_IPV6 is not set
>> >> CONFIG_FEATURE_PREFER_IPV4_ADDRESS=y
>> >> # CONFIG_VERBOSE_RESOLUTION_ERRORS is not set
>> >> # CONFIG_ARP is not set
>> >
>> >This change doesn't look very desirable to me. What's the reason for
>> >it?
>>
>> As long as you don't have ipv6 in distro features somehow, ipv6 will
>> not be available. See introductory message of this series.
>
>Ah, so you're saying that ipv6 is missing from micro's DISTRO_FEATURES?
yes, like from any other distro, and like ipv4 or nls etc..
>If that's the case then it's just a bug: presumably it's been harmless
>in the past because very few packages care about it. Irrespective of
>that, the intended behaviour is that micro should be IPv6-enabled and
>turning it off in busybox does not seem like a good idea.
>
>Actually, a quick "grep -ri ipv6" in conf/distro didn't turn up any
>matches at all
exactly. Thus my RFC for feature/dep handling heuristics.
> so enabling IPv6 by DISTRO_FEATURES doesn't seem to be
>terribly well entrenched at the moment. If it were to be introduced
>then I suspect it would need to be a negative property (i.e. the feature
>would be "no ipv6") in order to not break all the existing distros.
I disagree. Distros should be fixed to ask for or require a feature if
they require it.
For a nice way to flag packages with HANDLED_FEATURES, see conversation
with kergoth from today, around 18:00 UTC.
next prev parent reply other threads:[~2010-06-09 19:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 15:31 [PATCH] uClibc: rename main include Bernhard Reutner-Fischer
2010-02-22 5:54 ` Khem Raj
2010-03-12 17:46 ` [RFC, PATCH 0/3] uClibc recipe touchup Bernhard Reutner-Fischer
2010-03-12 17:46 ` [PATCH 1/3] uClibc: rename include file of old releases Bernhard Reutner-Fischer
2010-03-12 17:46 ` [PATCH 2/3] sane-toolchain: add PREFERRED_UCLIBC_VERSION Bernhard Reutner-Fischer
2010-04-05 19:49 ` Roman I Khimov
2010-04-08 9:30 ` Stefan Schmidt
2010-06-09 17:11 ` Bernhard Reutner-Fischer
2010-03-12 17:46 ` [PATCH 3/3] uClibc: redo configuration Bernhard Reutner-Fischer
2010-04-05 20:22 ` Roman I Khimov
2010-06-09 17:10 ` [PATCH 0/3] uClibc configury touchup; RFC WRT feature/dep picking heuristics Bernhard Reutner-Fischer
2010-06-09 21:26 ` RFC " Bernhard Reutner-Fischer
2010-06-09 17:10 ` [PATCH 1/3] uClibc: redo configuration Bernhard Reutner-Fischer
2010-06-09 17:10 ` [PATCH 2/3] uclibc_git: keep PV at "git" Bernhard Reutner-Fischer
2010-06-09 17:10 ` [PATCH 3/3] busybox: picking IPv6 per default is not up to the package Bernhard Reutner-Fischer
2010-06-09 18:44 ` Phil Blundell
2010-06-09 18:52 ` Bernhard Reutner-Fischer
2010-06-09 19:18 ` Phil Blundell
2010-06-09 19:32 ` Bernhard Reutner-Fischer [this message]
2010-06-09 20:22 ` Phil Blundell
2010-06-10 19:46 ` [PATCH 1/2] uclibc: handle DISTRO_FEATURE="largefile" Bernhard Reutner-Fischer
2010-06-10 19:46 ` [PATCH 2/2] busybox: configure according to {MACHINE, DISTRO}_FEATURES Bernhard Reutner-Fischer
2010-06-10 19:55 ` Chris Larson
2010-06-10 20:22 ` Phil Blundell
2010-06-10 20:27 ` Chris Larson
2010-06-10 20:50 ` Bernhard Reutner-Fischer
2010-06-10 21:06 ` Phil Blundell
2010-06-10 21:20 ` Bernhard Reutner-Fischer
2010-06-11 12:59 ` Phil Blundell
2010-06-22 20:39 ` Bernhard Reutner-Fischer
2010-06-28 18:23 ` ping**2 [was: Re: [PATCH 2/2] busybox: configure according to {MACHINE, DISTRO}_FEATURES] Bernhard Reutner-Fischer
2010-06-10 22:56 ` [PATCH 2/2] busybox: configure according to {MACHINE, DISTRO}_FEATURES Khem Raj
2010-06-11 7:16 ` Bernhard Reutner-Fischer
2010-06-10 20:44 ` Bernhard Reutner-Fischer
2010-06-10 21:09 ` 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=20100609193242.GR14941@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=openembedded-devel@lists.openembedded.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