Summary: | Stupid USE="doc" managment in gnome2.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gilles Dartiguelongue (RETIRED) <eva> |
Component: | Eclasses | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | as.gentoo, betelgeuse, binki, brant, djcozatt, eric_chaligny, esigra, grzegorz, maekke, mirraz1, nikoli, pacho, pva, sandro.bonazzola, serkan, toralf, uzytkownik2, volkmar |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 247680, 249279, 258759, 262387, 264157, 265176, 265216, 268380, 270704, 347863 | ||
Bug Blocks: | 239524, 261701, 279856, 298560, 318475, 347903, 383901 | ||
Attachments: | Patch adding GCONF_GTKDOC="no" to not add gtk-doc to GCONF |
Description
Gilles Dartiguelongue (RETIRED)
![]() Created attachment 186668 [details, diff]
Patch adding GCONF_GTKDOC="no" to not add gtk-doc to GCONF
This patch has the same of GCONF_DEBUG wich can be set to "no" to prevent adding --enable-debug=yes when debug is enabled.
Here, GCONF_GTKDOC set to "no" prevents adding --[enable|disable]-gtk-doc.
It has a backward compatibility and it prevents QA warnings for ebuild using gnome2 eclass without gtk-doc option (like ekiga-3 for me).
*** Bug 280811 has been marked as a duplicate of this bug. *** Considering short meeting summary: - USE=doc management is inconsistent, and unflexible + It should atleast check for GTK_DOC_INIT before passing $(use_enable gtk-doc) + USE=doc means rebuilding of api-docs right now, advantages seem to be uncertain --> dang was doing research + Consensus was to use USE=doc for api-docs, and install user documentation unconditionally I approve of this patch with a few changes: * adding a default to the variable * adding eclass doc with it (at least for this variable) @herd, next question is, do we really want to rebuild the docs with USE="doc" ? It seems like gtkdoc-rebase is what is really interesting for us when using doc pre-generated by upstream, and it looks like a self-contained perl script. Maybe we can split it and always depend on it when USE="doc" and forget about rebuilding all the docs which is time consuming both for users and for us as they often are not checked before a release. This seems fine to me, assuming it can be reasonably done. I'd prefer to have the option to install API docs without rebuilding them, so I can avoid all the dependencies. gtkdoc-rebase sounds perfect. *** Bug 304701 has been marked as a duplicate of this bug. *** *** Bug 247680 has been marked as a duplicate of this bug. *** *** Bug 249279 has been marked as a duplicate of this bug. *** *** Bug 262387 has been marked as a duplicate of this bug. *** *** Bug 264157 has been marked as a duplicate of this bug. *** *** Bug 265216 has been marked as a duplicate of this bug. *** *** Bug 268380 has been marked as a duplicate of this bug. *** *** Bug 347863 has been marked as a duplicate of this bug. *** *** Bug 347903 has been marked as a duplicate of this bug. *** *** Bug 353313 has been marked as a duplicate of this bug. *** *** Bug 353310 has been marked as a duplicate of this bug. *** *** Bug 364579 has been marked as a duplicate of this bug. *** *** Bug 386099 has been marked as a duplicate of this bug. *** (In reply to comment #4) > This seems fine to me, assuming it can be reasonably done. I'd prefer to have > the option to install API docs without rebuilding them, so I can avoid all the > dependencies. gtkdoc-rebase sounds perfect. We should probably try to give a push to this and there are some problems related with rebuilding docs that could be avoided with this :-/ *** Bug 411561 has been marked as a duplicate of this bug. *** *** Bug 415079 has been marked as a duplicate of this bug. *** *** Bug 415083 has been marked as a duplicate of this bug. *** This is better handled with eapi5 |