From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: [PATCH] wireless-regdb: fix Makefile to prevent unintended rebuilds
Date: Fri, 09 Jan 2009 13:24:05 -0500 [thread overview]
Message-ID: <20090109182405.31872.62007.stgit@dv.roinet.com> (raw)
Rules depending on key.priv.pem should only be available if that file is
already present. They should not trigger automatic generation of
key.priv.pem.
"make clean" should not remove files that can only be generated by the
maintainer. Use "make maintainer-clean" for that.
"make clean" should remove *.pyc files.
Signed-off-by: Pavel Roskin <proski@gnu.org>
---
Makefile | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index 1d8ff2a..7a0749b 100644
--- a/Makefile
+++ b/Makefile
@@ -1,15 +1,21 @@
-.PHONY: all clean
+.PHONY: all clean maintainer-clean
all: regulatory.bin key.pub.pem
clean:
+ rm -f *.pyc
+
+maintainer-clean:
+ $(MAKE) clean
rm -f regulatory.bin key.pub.pem
+ifneq ($(wildcard key.priv.pem),)
regulatory.bin: db.txt key.priv.pem
./db2bin.py regulatory.bin db.txt key.priv.pem
key.pub.pem: key.priv.pem
openssl rsa -in key.priv.pem -out key.pub.pem -pubout -outform PEM
+endif
key.priv.pem:
openssl genrsa -out key.priv.pem 2048
reply other threads:[~2009-01-09 18:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090109182405.31872.62007.stgit@dv.roinet.com \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).