Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.05 released
Date: Sun, 30 May 2010 22:31:17 +0200	[thread overview]
Message-ID: <87iq65rv1m.fsf@macbook.be.48ers.dk> (raw)

Hi,

Buildroot 2010.05 is released - Go download it at:

http://buildroot.net/downloads/buildroot-2010.05.tar.gz

or

http://buildroot.net/downloads/buildroot-2010.05.tar.bz2

After 3 months of development a new stable Buildroot release is
out. Significant changes are:

 - Restructured/simplified 'make menuconfig' menus to make it easier to
   locate the packages you need. Remember you can search in menuconfig
   using '/' if you get lost.
 - Lots of fixes for better external toolchain support, including
   multilib toolchains.
 - Bunch of new packages and toolchain versions. Xorg 7.5. More
   accurate wchar/locale/gettext annotations.
 - Additional system dependencies checks to give clear error messages
   instead of various odd breakage at a later stage.
 - Additional package conversion to gentarget/autotools infrastructure.
   A similar infrastructure has been added for the filesystem
   outputs. Notice that this work changed the output filesystem
   filenames.
 - Added script to display package dependencies graphically
   (see ./scripts/graph-depends)
 - Unmaintained nios2 support removed

And the usual package version updates and bug fixes. See the CHANGES
file for details:

http://git.buildroot.net/buildroot/plain/CHANGES?id=2010.05

Quite some work has been done during this release (666 commits) -
Many thanks to the people contributing to this release:

git shortlog -s -n 2010.02..
   224  Paulius Zaleckas
   182  Thomas Petazzoni
   148  Peter Korsgaard
    28  Gustavo Zacarias
    26  Will Wagner
    14  Lionel Landwerlin
     6  Yann E. MORIN
     4  H Hartley Sweeten
     3  Darius Augulis
     3  Josh.Wu
     3  Luca Ceresoli
     2  Alexander Clouter
     2  Bj?rn Forsman
     2  Julien Boibessot
     2  Kelvin Cheung
     2  Paul Jones
     2  Richard van Paasen
     1  Baruch Siach
     1  Chris Seawood
     1  Frederik Vannoote
     1  Grant Edwards
     1  Johan Thelin
     1  Laine Walker-Avina
     1  Michael Roth
     1  Mike Crowe
     1  Nick Leverton
     1  Thomas Brandstetter
     1  William Wagner
     1  cmchao
     1  serj.kalichev

The next release is going to be 2010.08. Expect the first release
candidate in late July and the final release at the end of
August. Notice that I'm away on holidays the first 3 weeks of August,
so this schedule might slip slightly.

Stuff in the pipeline for 2010.08 includes:

 - Gentarget/autotools conversion of the remaining packages. See
   http://lists.busybox.net/pipermail/buildroot/2010-May/034868.html
   for current status
 - More external toolchain work and closer cooporation with
   crosstool-ng (http://ymorin.is-a-geek.org/projects/crosstool)
 - Further work on package uninstall / rebuild support
 - More permanent setup for regression tests

Thanks to everyone contributing and testing the release candidates!

-- 
Bye, Peter Korsgaard

                 reply	other threads:[~2010-05-30 20:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87iq65rv1m.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