In file included from /usr/include/podofo/podofo-base.h:27:0,
/usr/include/podofo/base/PdfDefines.h:66:28: fatal error: boost/config.hpp: No such file or directory
boost/config.hpp is provided by dev-libs/boost, but calibre doesn't have that package in it's DEPEND variable.
isn't this rather a podofo issue? or should calibre depend on podofo[boost]?
podofo installs the package "dev-util/boost-build", but, in one of the headers files that it installs (PdfDefines.h) there is an include of "boost/config.hpp", which is provided by dev-libs/boost. And that header file (PdfDefines.h) is included in others 96 podifo headers, so yes, I think podofo should RDEPEND on dev-libs/boost.
# cd /usr/include/podofo/ && grep -R boost *
# cd /usr/include/podofo/ && grep -R "PdfDefines.h" * | wc -l
How about if we add a virtual/podofo-build meta-package that pulls in podofo and boost. Then packages like calibre can put virtual/podofo-build in DEPEND and app-text/podofo in RDEPEND. This will make it possible to use a command like `emerge --depclean --with-bdeps=n` to remove the build-time only boost package (and virtual/podofo-build).
*** Bug 484662 has been marked as a duplicate of this bug. ***
(In reply to Zac Medico from comment #3)
> How about if we add a virtual/podofo-build meta-package that pulls in podofo
> and boost. Then packages like calibre can put virtual/podofo-build in DEPEND
> and app-text/podofo in RDEPEND. This will make it possible to use a command
> like `emerge --depclean --with-bdeps=n` to remove the build-time only boost
> package (and virtual/podofo-build).
Following discussion on the gentoo-dev mailing list, I've created virtual/podofo-build and added DEPEND of all calibre ebuilds. Conclusions from discussion:
1) We don't want calibre to DEPEND directly on boost, since it would be unfortunate to pull in boost if not needed (suppose that podofo was built with USE=boost disabled).
2) Virtuals are more flexible than the BADEPEND suggested in bug #392239. If we later find that virtual/podofo-build works for calibre but not some other reverse dependency of podofo, then we can always create a different virtual to put in DEPEND of said reverse-dependency.