The recent devel branch requires a2x to make rpm.
sed “s/%VERSION%/1.5/” docs/man/man1/ansible-pull.1.asciidoc.in > docs/man/man1/ansible-pull.1.asciidoc
ERROR: AsciiDoc ‘a2x’ command is not installed but is required to build docs/man/man1/ansible.1 docs/man/man1/ansible-playbook.1 docs/man/man1/ansible-pull.1 docs/man/man1/ansible-doc.1
make: *** [docs/man/man1/ansible-pull.1] Error 1
rm docs/man/man1/ansible-pull.1.asciidoc
What am I supposed to do about that?
Please provide details about what OS/version you are building the RPM on.
root@urk:~# apt-file search bin/a2x
asciidoc: /usr/bin/a2x
And "yum search asciidoc" comes up with results.
Does rpm.spec have a way to list a series of build dependencies? I'm a Debian guy, and that would be done thru debian/control:Build-Depends
Asciidoc produces no results on what platform? Confused by your apt-file command above.
It could be added to BuildRequires, though this is more for packaging relative to the tarball.
The build system will attempt to do this prior to building the RPM (and we are ok with this, because RPM is only one of many things we use and should not drive the build system)
We do “make rpm” from checkout, which calls the docs target.
Excerpts from Adam Heath's message of 2014-02-05 13:24:48 -0500:
root@urk:~# apt-file search bin/a2x
asciidoc: /usr/bin/a2xAnd "yum search asciidoc" comes up with results.
Does rpm.spec have a way to list a series of build dependencies? I'm a
Debian guy, and that would be done thru debian/control:Build-Depends
In the spec file, 'BuildRequires: asciidoc' in the metadata section at
the top of the file.
This is because there are pre-build steps that happen before the package build step.
Adding it to BuildRequires hurts nothing, but it would not build the docs (which is ok, as they are in the release tarball that the RPM build references).