From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] RFC: Unifying the behavior of the doc use flag and document it
Date: Sat, 23 Jun 2007 17:11:16 +0300 [thread overview]
Message-ID: <467D2A04.6080504@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
For example the gnome people use the doc use flag to control whether
gtk-doc gets rebuild using cross references:
16:51 <@leio> as far as I'm concerned the doc USE flag means rebuilding
documentation to get cross-referencing in docs working
16:51 <@leio> also the lack of doc USE flag does not mean to not install
documentation
16:52 <@leio> it means to not take a long time to build documentation,
and we are not doing it if doc USE flag is not present
This leads to having tons of gtk-doc installed:
betelgeuse@pena ~ $ du -sh /usr/share/gtk-doc/html/
51M /usr/share/gtk-doc/html/
In for example Java we use it to control Javadoc installation. Javadoc
generation rarely takes much time and needs no extra dependencies but
having Javadocs for everything would consume a lot of space.
My opinion is to make it clear that the doc use flag always controls
whether or not to install documentation and make it clear in the
devmanual. For what gnome does, they can then add for example a gtk-doc
use flag to control the building of the cross references and have the
doc use flag control the installation of the bundled documentation.
betelgeuse@pena ~ $ euse -i doc
global use flags (searching: doc)
************************************************************
[- ] doc - Adds extra documentation (API, Javadoc, etc)
INSTALL_MASK is of course a solution to not installing gtk-doc at all
but it doesn't give me the ability to install it only for individual
packages.
What do others think?
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next reply other threads:[~2007-06-23 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 14:11 Petteri Räty [this message]
2007-06-23 14:19 ` [gentoo-dev] RFC: Unifying the behavior of the doc use flag and document it Ciaran McCreesh
2007-06-23 14:45 ` Petteri Räty
2007-06-23 14:57 ` Ciaran McCreesh
2007-06-23 16:27 ` Mart Raudsepp
2007-06-25 1:58 ` Daniel Drake
2007-06-23 14:29 ` Marius Mauch
2007-06-23 14:34 ` Petteri Räty
2007-06-24 12:46 ` [gentoo-dev] " Steve Long
2007-06-24 13:42 ` Kent Fredric
2007-06-24 13:47 ` Ciaran McCreesh
2007-06-24 20:50 ` [gentoo-dev] " Steve Long
2007-06-25 14:07 ` Steve Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=467D2A04.6080504@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox