From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Unifying the behavior of the doc use flag and document it
Date: Sat, 23 Jun 2007 17:45:02 +0300 [thread overview]
Message-ID: <467D31EE.4030109@gentoo.org> (raw)
In-Reply-To: <20070623151917.35bd2b01@snowflake>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Ciaran McCreesh kirjoitti:
> On Sat, 23 Jun 2007 17:11:16 +0300
> Petteri Räty <betelgeuse@gentoo.org> wrote:
>> 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.
>
> The doc use flag is used where there is a reason to make documentation
> optional rather than mandatory. Examples of such reasons include
> increased dependencies (e.g. Doxygen, which pulls in a fair bit),
> increased build time (e.g. Doxygen, which can be frickin' slow) or
> substantially increased disk usage. If there's no substantial cost to
> documentation, it should always be installed.
>
Yep but we should for example document what constitues increased disk
usage. How about "several megabytes or tens of files"?
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-06-23 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 14:11 [gentoo-dev] RFC: Unifying the behavior of the doc use flag and document it Petteri Räty
2007-06-23 14:19 ` Ciaran McCreesh
2007-06-23 14:45 ` Petteri Räty [this message]
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=467D31EE.4030109@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