Summary: | dev-libs/glib (e.g. 2.26.1-r1) with USE="+doc" should not depend on dev-util/gtk-doc (e.g. ≥1.13) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Navid Zamani <navid.zamani> |
Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Navid Zamani
2011-04-29 17:02:21 UTC
*** This bug has been confirmed by popular vote. *** For Gnome packages and those as as strongly related as glib, 'doc' flag is used (among other) for '--enable-gtk-doc', which means 'rebuild docs', as html docs are installed anyway. Aaah, that clarifies it. Thanks. :) But I thought that “doc” enables/disables installing docs at all. So how come it installs them even with “-doc”? Shouldn’t there be separate “doc” (installs) and “builddoc” (actually builds them) flags? Oh, and just by the way: How do I know which ones are strongly related to glib? Does “equery d glib” suffice? Actually, it varies. Here I meant simply that packages, that mimic packaging scheme used by Gnome and use gtk-doc, tend to have html docs already generated in source tarball and in such case, they get installed. 'doc' useflag, while global, tends to be quite quirky in some of the cases. |