On 02/05/2014 12:30 PM, Michael DeHaan wrote:
Asciidoc produces no results on what platform? Confused by your
apt-file command above.
==
apt-get install apt-file
apt-file update
==
This will download the Contents-$arch.gz files from your debian mirror,
then build an index of file->package mapping. I used this to guess as
to which package might contain that program, because I don't know how to
do the same on redhat-based machines.
I then jumped onto a CentOS install, and did a search for the asciidoc
package, to verify it was available.
It could be added to BuildRequires, though this is more for packaging
relative to the tarball.
Yes, that's what he was attempting. If a required package is needed,
then it should be added to the distributation-specific way. For
reference, this *is* specified in debian/control:Build-Depends in
current ansible-git master.
On debian, dpkg-checkbuiddeps will read debian/control, and tell you
what you need to install. I don't know if rpm has something similar.
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)
Sure. But if someone actually *does* want to build an rpm, shouldn't
the requirements for doing so be documented? I'm confused by what you
meant here.
We do "make rpm" from checkout, which calls the docs target.
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
