path: root/support/gnuconfig
diff options
authorGravatar Thomas Petazzoni <thomas.petazzoni@bootlin.com>2019-05-28 22:34:12 +0200
committerGravatar Peter Korsgaard <peter@korsgaard.com>2019-05-30 12:33:34 +0200
commit93e4f2d5ed52e04f99797790af1c489770b9d9d6 (patch)
treeac07a28065404254029da7cf66fd65129de633d8 /support/gnuconfig
parent2b8b6767ab1cc803a888cca91730732945f95b85 (diff)
support/gnuconfig: update README.buildroot with reality
4 out of 5 packages who are not using autotools but needed their gnuconfig files updated were not complying with the recommandation in support/gnuconfig/README.buildroot. The fifth package was converted to be like the others: use UPDATE_CONFIG_HOOK as a <pkg>_POST_PATCH_HOOKS rather than calling the CONFIG_UPDATE macro directly. Now that all packages are consistent, update the README.buildroot file to match the reality. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'support/gnuconfig')
1 files changed, 1 insertions, 1 deletions
diff --git a/support/gnuconfig/README.buildroot b/support/gnuconfig/README.buildroot
index a71ed93010..7ba2a332a4 100644
--- a/support/gnuconfig/README.buildroot
+++ b/support/gnuconfig/README.buildroot
@@ -10,7 +10,7 @@ If for some reason your package does not use the autotools-package
infrastructure, you can request the config.guess and/or config.sub
files of your package to be updated by using:
- $(call CONFIG_UPDATE,directory-of-your-package-sources)
--- UPDATE ---
GNU config is now managed in git, so to update: