+++ This bug was initially created as a clone of Bug #446414 +++ llvm was apparently (based on bug #446414) not installing manpages. Now it does, but it's pulling in dev-python/sphinx to do it, which in turn is pulling in several other packages (dev-pyton/pygments, dev-python/docutils, dev-python/jinja, dev-pyton/markupsafe) that I'd rather avoid if possible, since the only reason llvm's installed here at all is to enable the llvm features in mesa, so it's unlikely I'll ever want/need to use llvm or its manpages directly, and if I do I can always remerge if necessary. Please either put this behind USE=doc as well, or create a new USE flag to put it behind, thus allowing users who wish, to avoid those extra deps. equery/euse say there's a couple manpage-related USE flag in-tree precedents to choose from. 1) USE=man, found in dev-cpp/libcmis and sys-apps/pkgcore, with a description "Build and install manpages" 2) USE=manpages, found in sys-auth/sssd, with a description "Build manpages with dev-libs/libxslt" Thanks.
I see two things to do here: 1) request upstream to ship pre-generated manpages in the tarballs, 2) ship pre-generated manpages ourselves in the meantime. What do you think, Bernard?
This sounds better to me than USE=man (man pages always around is better). And they can always be re-generated with USE=doc. I'll make a manpages tarball and update the ebuild accordingly
Fixed in current llvm-3.2 ebuild (the installed files do not change) Now USE=-doc will use pre-generated pages and does not depend on dev-python/sphinx (USE=doc will generate man pages as before)
Thanks a lot ;)
