From ebcfa987df4095a7805ff124ab648fb607c89215 Mon Sep 17 00:00:00 2001 From: "Arnout Vandecappelle (Essensium/Mind)" Date: Mon, 12 Nov 2012 10:08:28 +0000 Subject: pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard --- Makefile.legacy | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 Makefile.legacy (limited to 'Makefile.legacy') diff --git a/Makefile.legacy b/Makefile.legacy new file mode 100644 index 000000000..2e015a1e3 --- /dev/null +++ b/Makefile.legacy @@ -0,0 +1,13 @@ +# +# Makefile.legacy - support for backward compatibility +# +# This file contains placeholders to detect backward-compatibility problems. +# When a buildroot "API" feature is being deprecated, a rule should be added +# here that issues an error when the old feature is used. +# +# This file is not included if BR2_DEPRECATED is selected, so it is possible +# to bypass the errors (although that's usually a bad idea). + +ifeq ($(BR2_LEGACY),y) +$(error "You have legacy configuration in your .config! Please check your configuration.") +endif -- cgit v1.2.3