From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: limit -reconfigure and -rebuild actions
Date: Fri, 20 Jul 2012 22:27:22 +0200 [thread overview]
Message-ID: <20120720222722.5f89af04@skate> (raw)
In-Reply-To: <1342791572-18657-1-git-send-email-rbraun@sceen.net>
Hello Richard,
Le Fri, 20 Jul 2012 15:39:32 +0200,
Richard Braun <rbraun@sceen.net> a ?crit :
> The -reconfigure and -rebuild per package targets unconditionally
> recreate the root filesystem image by depending on the all target.
> Restrict their actions to their package instead.
>
> Signed-off-by: Richard Braun <rbraun@sceen.net>
Well, the use case for those targets was the following: I am making
modifications to the source code of a package (especially using the
OVERRIDE_SRCDIR mechanism) and I want to easily restart the build of
that package and recreate the filesystem image so that I can test the
new version of my package on the target. That's the reason why the
target restarts the build *and* recreates the target filesystem.
For the -reconfigure, the idea is the same: I made some changes that
affect the configure script, or changed configuration options, and I
want to restart the configure+build+install of my package and recreate
the target filesystem.
That's the original idea of those targets. That said, I am personally
open to making changes to their semantic, but I'd prefer to see what
the opinion of other people in the community.
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:[~2012-07-20 20:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 13:39 [Buildroot] [PATCH] pkg-infra: limit -reconfigure and -rebuild actions Richard Braun
2012-07-20 15:34 ` Émeric Vigier
2012-07-20 15:58 ` Richard Braun
2012-07-20 21:55 ` Émeric Vigier
2012-07-20 20:27 ` Thomas Petazzoni [this message]
2012-07-20 23:31 ` Richard Braun
2012-07-21 12:54 ` Thomas Petazzoni
2012-07-21 15:17 ` Richard Braun
2012-07-21 16:14 ` Samuel Martin
2012-07-22 18:27 ` Alex Bradbury
2012-12-14 13:49 ` Arnout Vandecappelle
2012-07-24 23:07 ` Arnout Vandecappelle
2012-08-02 13:28 ` Alex Bradbury
2012-08-02 13:36 ` Thomas Petazzoni
2012-09-21 16:57 ` Alex Bradbury
2012-07-22 19:20 ` Stephan Hoffmann
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=20120720222722.5f89af04@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