git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Ward Comfort <icomfort@stanford.edu>
To: git@vger.kernel.org
Subject: [PATCH/RFC v2] RPM spec: optionally include bash completion support
Date: Fri, 19 Mar 2010 17:32:14 -0700	[thread overview]
Message-ID: <1269045134-28072-1-git-send-email-icomfort@stanford.edu> (raw)

Include the bash completion routines from contrib/ in our core RPM, in the
standard system-wide location, when our spec is built "--with completion". The
completion routines are not packaged by default.
---

 git.spec.in |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/git.spec.in b/git.spec.in
index ee74a5e..65a0db8 100644
--- a/git.spec.in
+++ b/git.spec.in
@@ -1,4 +1,5 @@
 # Pass --without docs to rpmbuild if you don't want the documentation
+# Pass --with completion to rpmbuild if you want shell completion support
 
 Name: 		git
 Version: 	@@VERSION@@
@@ -127,6 +128,11 @@ find $RPM_BUILD_ROOT -type f -name perllocal.pod -exec rm -f {} ';'
 rm -rf $RPM_BUILD_ROOT%{_mandir}
 %endif
 
+%if %{?_with_completion:1}0
+mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/bash_completion.d
+install -m 644 -T contrib/completion/git-completion.bash $RPM_BUILD_ROOT%{_sysconfdir}/bash_completion.d/git
+%endif
+
 %clean
 rm -rf $RPM_BUILD_ROOT
 
@@ -136,6 +142,7 @@ rm -rf $RPM_BUILD_ROOT
 %doc README COPYING Documentation/*.txt
 %{!?_without_docs: %doc Documentation/*.html Documentation/howto}
 %{!?_without_docs: %doc Documentation/technical}
+%{?_with_completion: %{_sysconfdir}/bash_completion.d}
 
 %files svn
 %defattr(-,root,root)
-- 
1.7.0.2

             reply	other threads:[~2010-03-20  0:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  0:32 Ian Ward Comfort [this message]
2010-03-20 18:18 ` [PATCH] Add a git-completion rpm subpackage to the spec Ben Walton
2010-03-20 20:12   ` Junio C Hamano
2010-03-20 21:01     ` Ian Ward Comfort
2010-03-20 21:14     ` Ben Walton
2010-03-21  1:20       ` Junio C Hamano
2010-03-21 15:51       ` Todd Zullinger
2010-03-21 20:06         ` Ben Walton

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=1269045134-28072-1-git-send-email-icomfort@stanford.edu \
    --to=icomfort@stanford.edu \
    --cc=git@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 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).