[Buildroot] List of pending patches: what to do?

[Thomas De Schampheleire]

On Fri, Aug 2, 2013 at 10:50 AM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> 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>.

As said, I don't have a problem with the existing
reconfigure-does-it-all approach.
I may have misunderstood the objections of others: there is no
objection against reconfigure doing also rebuild, only that
reconfigure and rebuild also make the rootfs?