From: Marc Lindahl <marc@bowery.com>
To: buildroot@busybox.net
Subject: [Buildroot] base busybox version for buildroot?
Date: Mon, 31 Jul 2006 20:15:25 -0400 [thread overview]
Message-ID: <9aa77677255835d7244f93dc4ed4b2f9@bowery.com> (raw)
In-Reply-To: <200607312012.48613.rob@landley.net>
On Jul 31, 2006, at 8:12 PM, Rob Landley wrote:
> On Thursday 27 July 2006 2:37 pm, Erik Andersen wrote:
>> On Thu Jul 27, 2006 at 09:44:42AM -0400, Drew Cohan wrote:
>>> Hi,
>>>
>>> Is the base busybox version for buildroot is now 1.2.0, instead of
>>> 1.1.3? Is there a buildroot config somewhere that determines which
>>> version of busybox is used, or is it just based on the date of the
>>> buildroot package (builds after 30 June 2006 use busybox 1.2.0)?
>>> There seems to have been a file size change recently, just curious
>>> what that might have been:
>>>
>>> buildroot-20060710.t..> 10-Jul-2006 00:17 3.8M
>>> buildroot-20060711.t..> 11-Jul-2006 00:17 4.3M
>>
>> It probably makes sense at this point to have configurable
>> busybox versions (as with gcc and binuitls) with a specific
>> default config for each.
>
> I still think the latest release version is all you need, but what do I
> know? :)
>
If you're building an embedded system you definitely want control over
the version... so you can freeze it once everything works, and ship it!
:)
just my $0.002
Marc
next prev parent reply other threads:[~2006-08-01 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 6:45 [Buildroot] base busybox version for buildroot? Drew Cohan
2006-07-27 11:38 ` Erik Andersen
2006-08-01 0:12 ` Rob Landley
2006-08-01 0:15 ` Marc Lindahl [this message]
2006-08-01 0:37 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 12:00 Daniels, Brian
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=9aa77677255835d7244f93dc4ed4b2f9@bowery.com \
--to=marc@bowery.com \
--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