From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2014.02-rc1 released
Date: Thu, 13 Feb 2014 23:36:25 +0100 [thread overview]
Message-ID: <20140213233625.0515088b@skate> (raw)
In-Reply-To: <87sirpvn7f.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Tue, 11 Feb 2014 13:38:28 +0100, Peter Korsgaard wrote:
> Of noteworthy new features we have:
>
> - Support for external packages/defconfigs (BR2_EXTERNAL). See user
> manual for details.
>
> - Cleanup of environment variable names for consistency. The download
> directory location override (BUILDROOT_DL_DIR) is now called
> BR2_DL_DIR. Likewise the name of the current .config is renamed from
> BUILDROOT_CONFIG to BR2_CONFIG. Please update your post build scripts
> if you use this!
>
> - Toolchains: uClibc pread/pwrite fixes, GCC stack corruption on ARM
> fix, updated Linaro and Sourcery Codebench external toolchains.
> Internal toolchain support for Microblaze.
>
> - Python package infrastructure support. See user manual for details.
I believe another very important feature is also the Luarocks package
infrastructure. You're mentioning luarocks amongst the new package
below, but I believe it would be good to highlight the fact that
luarocks is not just a new package: it is a whole new package
infrastructure that makes it easier to add Lua packages in Buildroot.
Maybe something to be added in the final release e-mail :)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-13 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 12:38 [Buildroot] Buildroot 2014.02-rc1 released Peter Korsgaard
2014-02-13 22:36 ` Thomas Petazzoni [this message]
2014-02-14 7:49 ` Peter Korsgaard
2014-02-14 7:50 ` Thomas De Schampheleire
2014-02-14 9:13 ` Peter Korsgaard
2014-02-14 9:22 ` Thomas Petazzoni
2014-02-14 9:25 ` 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=20140213233625.0515088b@skate \
--to=thomas.petazzoni@free-electrons.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