From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] List of pending patches: what to do?
Date: Fri, 2 Aug 2013 10:50:07 +0200 [thread overview]
Message-ID: <20130802105007.6957b0da@skate> (raw)
In-Reply-To: <CAAXf6LXdqkH1ccdDNdUVdriKxKur3f8ZtV58AaCsQPspUxMLaw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Fri, 2 Aug 2013 10:33:18 +0200, Thomas De Schampheleire wrote:
> I am currently used to -reconfigure and -rebuild to rebuild also the
> rootfs, but I also agree it's inconsistent with the other targets. If
> we want to be strict, then foo-reconfigure can only configure, not
> build. And foo-rebuild can only build.
Yerk, that's a bit ugly. foo-reconfigure removes the configure, build
stamp files as well as the host, staging, images and target install
stamp files. foo-rebuild does the same, except for the configure stamp
file.
So, I would find it strange if foo-reconfigure only did the configure
again and not the entire package build process. Same for foo-rebuild.
Remember, the use case for those is someone who is actively working on
the source code of a package (mainly when using the OVERRIDE_SRCDIR
thing or the local site method) and wants to be able to restart the
build of the package, just as if he was running 'make && make install'
in his package source code.
So the intention is really to have 'make foo-rebuild' do that 'make &&
make install' for the user, for the package <foo>.
Best 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:[~2013-08-02 8:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 17:14 [Buildroot] List of pending patches: what to do? Thomas Petazzoni
2013-07-31 17:18 ` Thomas Petazzoni
2013-07-31 20:44 ` Yann E. MORIN
2013-08-01 5:39 ` Thomas Petazzoni
2013-07-31 17:51 ` Gustavo Zacarias
2013-08-01 5:50 ` Thomas Petazzoni
2013-07-31 20:45 ` Thomas De Schampheleire
2013-07-31 20:57 ` Yann E. MORIN
2013-08-01 5:59 ` Thomas Petazzoni
2013-08-01 20:24 ` Yann E. MORIN
2013-07-31 20:55 ` Yann E. MORIN
2013-08-01 6:04 ` Thomas Petazzoni
2013-07-31 22:13 ` Samuel Martin
2013-07-31 22:20 ` Yann E. MORIN
2013-08-01 16:23 ` Thomas Petazzoni
2013-08-01 21:30 ` Samuel Martin
2013-08-02 8:33 ` Thomas De Schampheleire
2013-08-02 8:50 ` Thomas Petazzoni [this message]
2013-08-02 9:09 ` Thomas De Schampheleire
2013-08-02 9:10 ` Thomas Petazzoni
2013-08-02 9:27 ` Thomas De Schampheleire
2013-08-12 21:01 ` Arnout Vandecappelle
2013-08-01 2:52 ` Danomi Manchego
2013-08-01 6:13 ` Thomas Petazzoni
2013-08-01 20:14 ` Yann E. MORIN
2013-08-01 6:54 ` Simon Dawson
2013-08-01 7:41 ` Thomas Petazzoni
2013-08-01 16:16 ` Thomas Petazzoni
2013-08-02 8:10 ` Jérôme Pouiller
2013-08-02 11:11 ` Patrick Ziegler
2013-08-02 11:17 ` Thomas Petazzoni
2013-08-19 10:35 ` Luca Ceresoli
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=20130802105007.6957b0da@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