From: "Loïc Minier" <lool+kernel@via.ecp.fr>
To: linux-sparse@vger.kernel.org
Subject: Debian package; trivial fixes
Date: Thu, 9 Nov 2006 16:19:12 +0100 [thread overview]
Message-ID: <20061109151912.GC8508@bee.dooz.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
Hi,
I've prepared and uploaded a Debian package for sparse 0.1:
<http://people.dooz.org/~lool/debian/sparse/0.1-1/sid-pbuilder/>
FYI, It is currently targetted at Debian "non-free" due to the choice
of venue clause in the license. I think the patent clause is slightly
problematic but might be acceptable for Debian "main".
Please find attached a trivial fix for .gitignore where "check" wasn't
renamed to "sparse".
It would also be more convenient to create BINDIR automatically on make
install.
Bye,
--
Loïc Minier <lool@dooz.org>
[-- Attachment #2: rename-sparse-in-dot-gitignore.patch --]
[-- Type: text/plain, Size: 241 bytes --]
diff --git a/.gitignore b/.gitignore
index 3e12ce7..665ad03 100644
--- a/.gitignore
+++ b/.gitignore
@@ -11,9 +11,9 @@ pre-process.h
test-lexing
test-parsing
obfuscate
-check
compile
graph
+sparse
test-dissect
test-linearize
example
[-- Attachment #3: create-bindir.patch --]
[-- Type: text/plain, Size: 550 bytes --]
diff --git a/Makefile b/Makefile
index 2dcd514..920fe67 100644
--- a/Makefile
+++ b/Makefile
@@ -40,18 +40,12 @@ LIBS=$(LIB_FILE)
all: $(PROGRAMS)
-install: $(INST_PROGRAMS) bin-dir
+install: $(INST_PROGRAMS)
+ install -d $(BINDIR)
for f in $(INST_PROGRAMS); do \
install -v $$f $(BINDIR)/$$f || exit 1; \
done
-bin-dir:
- @if ! test -d $(BINDIR); then \
- echo "No '$(BINDIR)' directory to install in"; \
- echo "Please create it and add it to your PATH"; \
- exit 1; \
- fi
-
.PHONY: bin-dir
test-lexing: test-lexing.o $(LIBS)
next reply other threads:[~2006-11-09 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 15:19 Loïc Minier [this message]
2006-11-21 16:51 ` Debian package; trivial fixes Josh Triplett
2006-11-21 17:08 ` Josh Triplett
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=20061109151912.GC8508@bee.dooz.org \
--to=lool+kernel@via.ecp.fr \
--cc=linux-sparse@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.