From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: limit -reconfigure and -rebuild actions
Date: Fri, 14 Dec 2012 14:49:25 +0100 [thread overview]
Message-ID: <50CB2E65.10100@mind.be> (raw)
In-Reply-To: <CA+wH294311rh_e5HP8itswfG149Or1bOoKQ_GzAymRhVPRW9eA@mail.gmail.com>
On 22/07/12 20:27, Alex Bradbury wrote:
> On 21 July 2012 17:14, Samuel Martin<s.martin49@gmail.com> wrote:
>> Hi all,
>>
>> Here, I'll try to sum up what we talked few days ago on the IRC
>> channel, plus give my opinion about this.
>>
>> To be honest, the first time i tried these -reconfigure and -rebuild
>> targets, I was surprised they didn't behave as I would expect from
>> targets named like that, rebuilding not only the package but the
>> images too. So, I keep doing things by hands... though I understand
>> why things were implemented like this.
>
> I'm a newcomer to buildroot and was surprised by the effect of
> -reconfigure and -rebuild. I'd read about them in the slides from one
> of Tom's talks, and given their description I had assumed they would
> rebuild only the package. Reading the responses here, I can see why it
> is useful to have a target that rebuilds a single package and also
> makes the image (though really, it seems not that hard for the user to
> do another make command to build the image in that case). I would love
> to see a build target with the proposed semantics.
A colleague of mine (again) made this remark to me today... So, will we
accept this change or not?
Clearly it changes the behaviour, but I don't expect people will use
-rebuild or -reconfigure in scripts so it shouldn't hurt.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-12-14 13:49 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
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 [this message]
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=50CB2E65.10100@mind.be \
--to=arnout@mind.be \
--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