All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: move system.mk recipes inside the "target-finalize" rule
Date: Wed, 11 Jun 2014 14:54:35 +0200	[thread overview]
Message-ID: <20140611145435.40a60312@free-electrons.com> (raw)
In-Reply-To: <CAHkwnC9RPGoZcp4bqffN5yCnWRJoeRxKFf72JmrwwAFr3jCnyg@mail.gmail.com>

Dear Fabio Porcedda,

On Wed, 11 Jun 2014 11:21:38 +0200, Fabio Porcedda wrote:

> > Ah. I don't remember. Do you have a pointer to this discussion? I'd
> > like to see what were the arguments back then :-)
> 
> Sure: http://lists.busybox.net/pipermail/buildroot/2014-April/095052.html

Ok, I see now. The problem I have with the reasoning we used during
this discussion is that we only thought of those "global"
target-finalize tasks. But there are also plenty of more
package-specific ones, such as cleaning up unneeded Python things, or
unneeded Perl things. A hook mechanism would allow to move these
individual bits of logic down to the package needing them.

It's true that I admit it would be less easy to read and understand
that a complete list of all target-finalize tasks. So if Peter and
Arnout prefer the explicit list, I'm fine.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-06-11 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  8:52 [Buildroot] [PATCH] system: move system.mk recipes inside the "target-finalize" rule Fabio Porcedda
2014-06-10 20:33 ` Thomas Petazzoni
2014-06-11  9:14   ` Fabio Porcedda
2014-06-11  9:18     ` Thomas Petazzoni
2014-06-11  9:21       ` Fabio Porcedda
2014-06-11 12:54         ` Thomas Petazzoni [this message]
2014-06-11 16:32     ` Arnout Vandecappelle
2014-06-11 17:36       ` Thomas Petazzoni
2014-06-12  7:20       ` Fabio Porcedda
2014-06-12  7:32         ` Fabio Porcedda
2014-06-12  7:56           ` Thomas Petazzoni
2014-06-12  8:05             ` Fabio Porcedda
2014-06-12  8:23               ` Thomas Petazzoni
2014-06-12 12:54                 ` Arnout Vandecappelle
2014-06-19 10:06                   ` Fabio Porcedda

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=20140611145435.40a60312@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.