From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] 2009.02-rc2 released
Date: Mon, 26 Jan 2009 17:23:33 +0100 [thread overview]
Message-ID: <87bptu6np6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1232922252.2298.34.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Sun\, 25 Jan 2009 23\:24\:12 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> Now it works, regardless if you have X or not.
Ulf> so we and the user do not have to choose.
Ulf> If X is available you have a better experience.
We've mentioned several times that xconfig isn't necessarily a better
experience (E.G. it's inconsistent with BR and the busybox/uclibc
-menuconfig targets, unusable on slow links and pops up in another
window, effectively blocking the build without output until the user
figures that out, ..)
The default needs to be menuconfig like it was before.
>> But why? Just use menuconfig and be done with it. What does xconfig
>> bring you that menuconfig doesn't?
Ulf> Ease of use - ?menuconfig is archaic
Ulf> I would prefer to use Xconfig for Buildroot as well.
With that mindset you probably think the entire concept of BR is
arhaic ;)
Ulf> You want to minimize the options for the user, so I suggest
Ulf> that you write a new way of configuring Linux
Ulf> so you can do it the way You want.
>>
>> Sigh. Ulf, you really need to learn to work with the rest of the BR
>> developers.
Ulf> If people have valid issues, then I listen,
Ulf> My main problem is that not only does people want to
Ulf> to it in a certain way, they also want to ensure
Ulf> that it is not possible to do it in another way.
Ulf, I think you need to read
http://udrepper.livejournal.com/7326.html and then think about the
costs involved with adding configuration options (for the developers
AND for the users).
Ulf> If you want to ensure that Buildroot does not crash
Ulf> when people select to use make *-config, then that is
Ulf> a valid concern.
Ulf> If you want to ensure that Buildroot users
Ulf> are coreced into using menuconfig, then I think it is not.
s/menuconfig/xconfig/.
Ulf> If you want to ensure that people has to spend tons of time,
Ulf> updating the config file to fit their desires
Ulf> every time they download the trunk, again, I am against that.
Ulf> IMO, the submitted solution should meet all valid concerns.
with default = menuconfig it does, so that's what I'll change it to.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-26 16:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 0:28 [Buildroot] 2009.02-rc2 released Paul Jones
2009-01-25 7:32 ` Ulf Samuelsson
2009-01-25 13:07 ` Peter Korsgaard
2009-01-25 21:17 ` Ulf Samuelsson
2009-01-25 21:28 ` Peter Korsgaard
2009-01-25 22:24 ` Ulf Samuelsson
2009-01-25 23:52 ` Paul Jones
2009-01-26 5:54 ` Peter Korsgaard
2009-01-26 8:48 ` Cyril HAENEL
2009-01-26 16:23 ` Peter Korsgaard [this message]
2009-01-26 12:04 ` Thomas Lundquist
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 21:12 Peter Korsgaard
2009-01-23 21:27 ` Cyril HAENEL
2009-01-24 9:02 ` Peter Korsgaard
2009-01-24 13:03 ` Cyril HAENEL
2009-01-26 17:24 ` Robert Nelson
2009-01-26 17:43 ` Peter Korsgaard
2009-01-26 18:30 ` Robert Nelson
2009-01-26 18:49 ` Peter Korsgaard
2009-01-28 8:47 ` Hinko Kocevar
2009-01-28 16:37 ` Peter Korsgaard
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=87bptu6np6.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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