From: Ryan Anderson <ryan@michonline.com>
To: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] Deb packaging needs two more configuration files
Date: Fri, 22 Jul 2005 02:36:07 -0400 [thread overview]
Message-ID: <20050722063607.GS20369@mythryan2.michonline.com> (raw)
In-Reply-To: <20050722055556.GR20369@mythryan2.michonline.com>
The deb package building needs these two new files to work correctly.
debian/compat sets the rules under which the debhelper scripts (dh_*) operate.
debian/git-core.install tells dh_install what files to install in each package
that is generated. There is only one package being generated, so all files go
into it.
(I missed these in the last patch, mostly because I needed to do this to
find stuff I had missed:
find . -name .git -type d -prune -o -type f -print \
| grep -v -e .tree1 -e .tree2 \
| sed -e "s/^\.\///" \
| sort >.tree1
git-ls-files | grep -v -e .tree1 -e .tree2 \
| sort >.tree2
diff -u .tree1 .tree2
)
Signed-off-by: Ryan Anderson <ryan@michonline.com>
---
debian/compat | 1 +
debian/git-core.install | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
create mode 100644 debian/compat
create mode 100644 debian/git-core.install
d5ccc10c30f1baa968705aa0c3dfc98e0ade5eaf
diff --git a/debian/compat b/debian/compat
new file mode 100644
--- /dev/null
+++ b/debian/compat
@@ -0,0 +1 @@
+4
diff --git a/debian/git-core.install b/debian/git-core.install
new file mode 100644
--- /dev/null
+++ b/debian/git-core.install
@@ -0,0 +1 @@
+*
next prev parent reply other threads:[~2005-07-22 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 6:15 [PATCH] Deb packages should include the binaries Ryan Anderson
2005-07-22 5:55 ` [PATCH] Deb packages should include the binaries (Try 2 - this time it actually applies) Ryan Anderson
2005-07-22 6:36 ` Ryan Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-23 5:32 [PATCH] Deb packaging needs two more configuration files Junio C Hamano
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=20050722063607.GS20369@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox