I'm packaging a beta release where the tarball has a name like:
foobar-0.1.2-20040127.tar.bz2
(I have no control over the naming convention used upstream in this case)
### foobar.spec ###
%define beta 20040127
Name: foobar
Version: 0.1.2
Release: 0.repo.1
... snip ...
%prep
%setup -n %{name}-%{version}-%{beta}
... snip ...
######
When extracted, the directory contains docs in the following hierarchy:
ls -R .
.:
bar DOC1 DOC2 DOC3 foo
./bar:
DOC1 DOC2 DOC3
./foo:
DOC1 DOC2 DOC3
"make install" does *not* install any docs in this package.
Question 1) ... How can I control %doc to make it install to
%{_defaultdocdir}/%{name}-%{version}-%{beta} instead of
%{_defaultdocdir}/%{name}-%{version} ??
Question 2) ... How can I tell %doc to recreate the folder hierarchy as it
stands, with subdirectories?
If I can't do any of this with %doc, and I have to simply %{__install} all
the docs manually, then I'll have to remove %doc from the %files manifest
altogether ... which is B.A.D.® ... right?
TIA.
-
K.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
