Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Stable release?
Date: Mon, 14 Jul 2008 21:12:02 +0200	[thread overview]
Message-ID: <878ww48em5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20080714181515.GA7760@cbg.dyndns.org> (Steffen Schulz's message of "Mon\, 14 Jul 2008 20\:15\:15 +0200")

>>>>> "Steffen" == Steffen Schulz <pepe_ml@gmx.net> writes:

 Steffen> Hi all,

 Steffen> First of all many thanks to the developers of buildroot and
 Steffen> stuff like uclibc and busybox. You're doing great work!

Thanks.

 Steffen> I found buildroot to be the optimal solution for the system
 Steffen> engineering I do at work. Other distros are less flexible,
 Steffen> outdated or more difficult to modify. I'd also love to use
 Steffen> buildroot on my OLPC, ideally with the gentoo portage
 Steffen> package to add more programs later on.


 Steffen> So my question is, will there ever be a 'stable' release of
 Steffen> buildroot?  Do you aim for a system where all packages tend
 Steffen> to compile smoothly or do you continue to add new software
 Steffen> versions as long as some of the stuff builds?

I sure hope so! There has been discussions about it on and off, but we
have quite limited man power, so I hasn't happened yet. I'm setting up
a regression testing system (with buildbot) which will hopefully help
us getting there. Preferably we should have time based releases
(E.G. something like every 6 months).

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-07-14 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 18:15 [Buildroot] Stable release? Steffen Schulz
2008-07-14 19:12 ` Peter Korsgaard [this message]
2008-07-14 20:05   ` [Buildroot] Rtai and comedi support Hornos Tamás

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=878ww48em5.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