Hello, On Mon, 17 Feb 2014, David C. Rankin wrote:
No dir on %doc line:
%doc AUTHORS ChangeLog COPYING LICENSE README /usr/doc/html /usr/doc/pdf /usr/doc/ps
%doc wants _relative_ paths as seen from the builddir. Well, except stuff outside of %docdir like %doc %{_mandir}/man1/foo.1.gz
<snip> Processing files: WordNet-3.0-2.x86_64 error: Two files on one line: /usr/doc/html error: Two files on one line: /usr/doc/pdf error: Can't mix special %doc with other forms: /usr/doc/ps
Move/copy /usr/doc stuff to ./ (i.e. the builddir) or copy/prune the doc subdirectories / stuff in the builddir (and delete the /usr/doc/ stuff). As done in the wordnet-package in Education (rm {html,pdf,ps}/Makefile or something like that). In other cases, I copy stuff from doc/ (where there are manpages, generated html etc. inside in doc or subdirs) to a temp-dir and then list the _contents_ of that temp-dir. Like I already wrote on the os-ML: %install [..] rm -rf tempdocs mkdir -p tempdocs/html cp -a doc/html/* tempdocs/html/ %files [..] %doc README FAQ doc/*.ps doc/*.pdf tempdocs/html IIRC, you'll see, it'll all nicely end up in the package. This is especially useful if you want subdirs in your docdir, in the example above, README, FAQ, *.ps and *.pdf will end up in the package docdir and tempdocs/html will be a subdir html inside that, e.g. /usr/share/doc/packages/foo/README /usr/share/doc/packages/foo/foo.pdf /usr/share/doc/packages/foo/html/index.html The trick is to use wildcards with purpose and I think that %doc takes names only (files or dirs) and discards directories. I'd have to dig in my .specs for a real sample.
So trying the %docdir for-all approach:
Don't.
HTH,
-dnh
--
"Being disintegrated makes me ve-ry an-gry!"