Patrick:
> Without the patch I made you will get an error that there are
> unpackaged files when you build --without gtk-doc.
Did you check the config.log in the module and make sure that
pkgtool is correctly passing along the --wihtout-gtk-doc argument
to the configure script? Note the config.log shows you at the
top the configure command it received. Sometimes useful for
seeing what options you built with (or if you want to re-run
configure by hand with the same options).
> These two spec files I wrote a patch for are the only packages that
> had these problems (I did a pkgtool build --without gtk-doc *.spec)
>
> It's not so much that the build fails or that the packages don't get
> created. They just don't get installed automaticly because in the
> BUILD area there are files in /usr/share/gtk-doc that don't get
> packaged when using --without gtk-doc.
The pkgtool argument is --without-gtk-doc and not "--without gtk-doc".
Are you sure you are running this properly? Note the following from
the spec-files/include/options.inc file:
#
# Option: --without-gtk-doc
#
# use --without-gtk-doc to disable building gtk-docs (it takes quite
# a while to build them)
# default: build gtk-doc API docs
#
%define option_with_gtk_doc %{?!_without_gtk_doc:1}%{?_without_gtk_doc:0}
%define option_without_gtk_doc %{?_without_gtk_doc:1}%{?!_without_gtk_doc:0}
---
Lastly, if you are seeing this problem with one module, I'd expect you
to see similar problems with *all* spec-files that build gtk-docs. You
don't discuss this. If you don't, please explain why. We shouldn't be
proposing changes to the spec-files until we understand the problem.
Brian
