From: Ciaran McCreesh <ciaranm@ciaranm.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 15:57:39 +0100 [thread overview]
Message-ID: <20070623155739.47099922@snowflake> (raw)
In-Reply-To: <467D31EE.4030109@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Sat, 23 Jun 2007 17:45:02 +0300
Petteri Räty <betelgeuse@gentoo.org> wrote:
> > 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"?
It's a package dependent quantity, and should be left up to individual
maintainers. Vim's documentation, for example, is a lot of files and a
lot of disk space, but it isn't shipped via USE="doc" because it's
considered by upstream to be a vital part of the package.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-23 15:02 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
2007-06-23 14:57 ` Ciaran McCreesh [this message]
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=20070623155739.47099922@snowflake \
--to=ciaranm@ciaranm.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