From: Pavel Roskin <proski@gnu.org>
To: git <git@vger.kernel.org>, Petr Baudis <pasky@suse.cz>
Subject: [PATCH] cogito rpm package to include manuals
Date: Tue, 01 Nov 2005 23:30:50 -0500 [thread overview]
Message-ID: <1130905850.9704.12.camel@dv> (raw)
The cogito rpm package created by "make rpm" lacks manual pages. I can
understand why manuals are not generated for local installations by
default (asciidoc is slow, and the commands are self-documented), but
rpm packages should be closer to perfection.
Since there is no way to install manuals without also installing the
text documentation, so the later is deleted after installation.
Nothing from the Documentation directory except tutorial-script should
be included as documentation.
Signed-off-by: Pavel Roskin <proski@gnu.org>
diff --git a/cogito.spec.in b/cogito.spec.in
index 080b988..1ed9305 100644
--- a/cogito.spec.in
+++ b/cogito.spec.in
@@ -8,6 +8,7 @@ URL: http://kernel.org/pub/software/sc
Source: http://kernel.org/pub/software/scm/cogito/%{name}-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
Requires: git-core >= 0.99.7
+BuildRequires: asciidoc
BuildArch: noarch
%description
@@ -21,11 +22,13 @@ many other version control systems.
%build
-make
+make all doc
%install
rm -rf $RPM_BUILD_ROOT
-make DESTDIR=$RPM_BUILD_ROOT prefix=%{_prefix} libdir=%{_libdir}/cogito install
+make DESTDIR=$RPM_BUILD_ROOT prefix=%{_prefix} libdir=%{_libdir}/cogito mandir=%{_mandir} \
+ install install-doc
+rm -rf $RPM_BUILD_ROOT/%{_prefix}/share/doc/cogito/txt
%clean
rm -rf $RPM_BUILD_ROOT
@@ -35,9 +38,13 @@ rm -rf $RPM_BUILD_ROOT
%{_bindir}/*
%dir %{_libdir}/cogito
%{_libdir}/cogito/*
-%doc README COPYING Documentation/*
+%{_mandir}/man*/*
+%doc README COPYING Documentation/tutorial-script
%changelog
+* Tue Nov 1 2005 Pavel Roskin <proski@gnu.org> 0.15.1-1
+- generate and include manuals
+
* Tue Oct 11 2005 Chris Wright <chrisw@osdl.org> 0.15.1-1
- use %dist
--
Regards,
Pavel Roskin
reply other threads:[~2005-11-02 4:31 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=1130905850.9704.12.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).