From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] inittab for Busybox
Date: Tue, 15 Mar 2011 21:05:38 +0100 [thread overview]
Message-ID: <20110315210538.1973f87f@surf> (raw)
In-Reply-To: <1D6034426110564DA0DEA9EE9793B3835815AE1A1F@NBE-MBX01.americas.swk.pri>
Hello,
On Tue, 15 Mar 2011 14:32:07 -0400
"Heyendal, Carl" <CHeyendal@stanleyworks.com> wrote:
> Really!! 'make clean' from Buildroot directory? That's a complete
> rebuild!!
Yes, it is. For now, Buildroot is "nothing" more but a tool that
automates the process of building an embedded Linux system. It is not
very smart, so it cannot remove packages that have been installed, or
revert changes that have been made to the target filesystem.
My view on this: Buildroot has been more or less abandonned until late
2008/early 2009, when Peter took over the maintainership of the
project. Since that time, our main goal was to clean up the existing
code base, keeping the existing feature set (in fact, we added a bunch
of features as well, but we didn't fundamentaly changed how Buildroot
works). Now that this cleanup process is mostly over, I'd say that
solving the issue you're facing here is now on the top priorities of
the project. At least it's where it is on my own Buildroot TODO list.
But there a fairly huge and complex amount of work to do here, so it
isn't going to happen overnight.
> How come then it picked up my other Busybox change without having to
> do a global re-build?
Because when you change the Busybox configuration, we have a make
dependency that makes sure that Busybox gets rebuilt/reinstalled.
But that does not happen when you unselect sysvinit.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-03-15 20:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:37 [Buildroot] inittab for Busybox Heyendal, Carl
2011-03-15 17:07 ` Thomas Petazzoni
2011-03-15 17:28 ` Charles Krinke
2011-03-15 18:14 ` Heyendal, Carl
2011-03-15 18:22 ` Thomas Petazzoni
2011-03-15 18:32 ` Heyendal, Carl
2011-03-15 20:05 ` Thomas Petazzoni [this message]
2011-03-15 20:10 ` Heyendal, Carl
2011-03-16 16:44 ` [Buildroot] Buildroot in use Steve Calfee
2011-03-16 20:08 ` Heyendal, Carl
2011-03-17 12:14 ` William Wagner
2011-03-17 13:53 ` Heyendal, Carl
2011-03-17 17:17 ` Steve Calfee
2011-03-17 19:42 ` Heyendal, Carl
2011-03-17 21:50 ` Steve Calfee
2011-03-18 16:03 ` Thomas Petazzoni
2011-03-18 16:02 ` Thomas Petazzoni
2011-03-18 16:01 ` Thomas Petazzoni
2011-03-17 20:21 ` Grant Edwards
2011-03-18 15:59 ` [Buildroot] Xtensa support Thomas Petazzoni
2011-03-21 21:18 ` Piet Delaney
2011-09-20 18:35 ` Thomas Petazzoni
2011-09-21 4:01 ` Marc Gauthier
2011-09-21 6:52 ` Thomas Petazzoni
2011-09-21 8:08 ` Piet Delaney
2011-03-27 19:19 ` [Buildroot] Buildroot in use Michael J. Hammel
2011-03-27 23:58 ` Steve Calfee
2011-03-31 17:13 ` Steve Calfee
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=20110315210538.1973f87f@surf \
--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