From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-2012.11 1/5] pkg-infra: introduce errors for legacy API
Date: Tue, 13 Nov 2012 09:51:40 +0100 [thread overview]
Message-ID: <20121113095140.034cf667@skate> (raw)
In-Reply-To: <50A167A6.5000705@mind.be>
On Mon, 12 Nov 2012 22:18:30 +0100, Arnout Vandecappelle wrote:
> > BR2_LEGACY here maybe?
>
> No that would not make sense - we want to get the error message if BR2_LEGACY
> is selected (automatically, by Config.in.legacy).
>
> The idea of the condition is to have an escape path, if you don't want to deal
> with all the stuff that is misconfigured (not only legacy config symbols but also
> host-pkg-config etc.), you can just build with BR2_DEPRECATED=y and see how far
> you get.
Aaah, ok.
Thanks!
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-11-13 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 20:08 [Buildroot] [PATCH for-2012.11 0/5] Introduce errors for legacy API Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 1/5] pkg-infra: introduce " Arnout Vandecappelle
2012-11-12 21:05 ` Thomas Petazzoni
2012-11-12 21:18 ` Arnout Vandecappelle
2012-11-13 8:51 ` Thomas Petazzoni [this message]
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 2/5] legacy: move old GENTARGETS macros to Makefile.legacy Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 3/5] legacy: add error target for host-pkg-config Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 4/5] legacy: evtest is dropped from input-tools package Arnout Vandecappelle
2012-11-12 20:08 ` [Buildroot] [PATCH for-2012.11 5/5] legacy: BR2_PACKAGE_LIBINTL is replaced by gettext Arnout Vandecappelle
2012-11-15 11:23 ` [Buildroot] [PATCH for-2012.11 0/5] Introduce errors for legacy API Peter Korsgaard
2012-11-23 14:59 ` Arnout Vandecappelle
2012-11-30 20:10 ` 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=20121113095140.034cf667@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