From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] selecting busybox releases
Date: Mon, 7 Aug 2006 20:36:35 -0400 [thread overview]
Message-ID: <200608072036.35524.rob@landley.net> (raw)
In-Reply-To: <19455.63.193.249.101.1154900344.squirrel@webmail.aerende.com>
On Sunday 06 August 2006 5:39 pm, jtesta at aerende.com wrote:
> Once I have a stable version of buildroot compiled,
> how do I guarantee that I always get the same version
> of the packages, say busybox for example?
>
> I tried unselecting the "Use the daily snaphost of Busybox"
> but that started to download another version.
I recommend using the release version of busybox unless you either want to
help us debug the thing or else need a specific new feature that wasn't in
the latest release version.
Daily snapshots of busybox can have all sorts of random half-finished stuff in
them, but we try to stabilize -devel into a new release every few months.
1.2.0 came out June 30, and 1.2.1 (a bugfixes only dot-release) was only a
week or two back. So at this point, the busybox -devel tree has only
accumulated a little over a month's worth of new changes, and we plan to have
our next release including the new development (1.3.0) in December.
uClibc may go a year between releases (technically it has 10 more days until
this is the case), and buildroot itself may never have an actual stable
release with a version number and everything, but the current BusyBox
maintainer is kind of big into the whole concept. :)
> Thanks,
>
> Jim
Rob
--
Never bet against the cheap plastic solution.
prev parent reply other threads:[~2006-08-08 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 21:39 [Buildroot] selecting busybox releases jtesta at aerende.com
2006-08-08 0:36 ` Rob Landley [this message]
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=200608072036.35524.rob@landley.net \
--to=rob@landley.net \
--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