Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Move host-pkgconf dependency to package/pkg-autotools.mk
Date: Sat, 11 Apr 2015 09:47:25 +0200	[thread overview]
Message-ID: <20150411094725.5c29b312@free-electrons.com> (raw)
In-Reply-To: <55284115.40309@mind.be>

Arnout,

On Fri, 10 Apr 2015 23:31:01 +0200, Arnout Vandecappelle wrote:

>  I agree that something like that is the way to go.
> 
>  However, I would prefer that this kind of stuff:
> 
> - goes into scripts in the support/ directory;
> 
> - gets called from the GLOBAL_INSTRUMENTATION_HOOKS;
> 
> - is selectable with a config option in the Build options menu (which would be
> enabled by the autobuilders).
> 
>  My reasoning is that the BR infrastructure is already pretty darn complicated,
> so it would be good to separate the core infrastructure from the fringe stuff.
> And the config option is of course because I prefer to keep the developer stuff
> out of the way of normal users.

I fully agree with these suggestions. I think you already made them on
my previous posting of a patch doing this check, and it's just that I
haven't taken the time to prepare a new version of the patch.

Thanks,

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

  reply	other threads:[~2015-04-11  7:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  9:33 [Buildroot] [RFC] Move host-pkgconf dependency to package/pkg-autotools.mk Bernd Kuhls
2015-04-10 10:52 ` Bernd Kuhls
2015-04-10 12:09   ` Thomas Petazzoni
2015-04-10 12:12 ` Thomas Petazzoni
2015-04-10 21:31   ` Arnout Vandecappelle
2015-04-11  7:47     ` Thomas Petazzoni [this message]
2015-04-21 14:13       ` Peter Korsgaard

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=20150411094725.5c29b312@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox