From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options
Date: Thu, 08 Jan 2015 21:36:53 +0100 [thread overview]
Message-ID: <54AEEA65.1040501@mind.be> (raw)
In-Reply-To: <20141231151734.0c95b119@free-electrons.com>
On 31/12/14 15:17, Thomas Petazzoni wrote:
> Hello,
>
> On Thu, 30 Oct 2014 23:03:10 +0100, Thomas Petazzoni wrote:
>
>> I was going to apply this, and then I tested it, to discover that it
>> then causes the same problem as the one we have with randpackageconfig
>> today: none of the choice options get randomized anymore. So before
>> this patch, if you do "randconfig", you get proper randomization. After
>> this patch, if you do "randconfig", it only generates i386
>> configurations.
>>
>> I admit it's not really an issue introduced by the patch as the issue
>> already exists for randpackageconfig. But it's very annoying :/
>
> Any comment about this?
Well, as you explained to me in Dusseldorf, the main reason to use randconfig
is to test against buggy Config.in depends/select chains. If the choices
wouldn't get properly randomized anymore, that would really kill this use case.
So I guess that's a no go.
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
next prev parent reply other threads:[~2015-01-08 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:24 [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options Arnout Vandecappelle
2014-10-14 9:24 ` [Buildroot] [PATCH v3 2/2] randconfig: seed with BR2_RAND_PRESEED_CONFIG_FILES Arnout Vandecappelle
2014-10-19 9:00 ` Yann E. MORIN
2014-10-30 22:03 ` [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options Thomas Petazzoni
2014-12-31 14:17 ` Thomas Petazzoni
2015-01-08 20:36 ` Arnout Vandecappelle [this message]
2015-01-08 20:43 ` Thomas Petazzoni
2015-01-24 23:00 ` Arnout Vandecappelle
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=54AEEA65.1040501@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.