From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Gratuitous useflaggery (doc and examples)
Date: Sat, 4 Mar 2006 01:04:39 +0000 [thread overview]
Message-ID: <20060304010439.30478098@snowdrop.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
This is undocumented and unofficial, so feel free to utterly ignore it
and commit whatever the heck you want.
The 'doc' and 'examples' (yay for consistency!) USE flags are intended
for use where building documentation or examples would take a long
time, introduce new dependencies or otherwise be an inconvenience to
many users.
For example, if libiamafish comes with a half dozen small example
source files and a few pages of HTML, just install them. If, however,
libiamafish requires, say, doxygen to generate its documentation, or
comes with several megabytes of examples in a separate tarball, then
you should consider a USE flag.
Explanation: a USE flag for trivial stuff that isn't in /etc, doesn't
slow anything down, doesn't introduce any dep bloat and generally
doesn't change anything noticeable isn't a USE flag that's giving the
user any meaningful choice or making things easier for arch teams. You
do not get bonus points for using more USE flags.
--
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next reply other threads:[~2006-03-04 1:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 1:04 Ciaran McCreesh [this message]
2006-03-04 15:15 ` [gentoo-dev] Gratuitous useflaggery (doc and examples) Stuart Herbert
2006-03-04 15:43 ` Dan Armak
2006-03-04 16:00 ` Carsten Lohrke
2006-03-04 18:20 ` Dan Armak
2006-03-06 16:39 ` Paul de Vrieze
2006-03-06 21:01 ` Carsten Lohrke
2006-03-06 21:11 ` Alec Warner
2006-03-04 16:03 ` Harald van Dijk
2006-03-04 15:56 ` [gentoo-dev] " MIkey
2006-03-04 17:02 ` Ferris McCormick
2006-03-04 18:04 ` [gentoo-dev] " MIkey
2006-03-04 18:13 ` Ciaran McCreesh
2006-03-04 18:18 ` [gentoo-dev] " MIkey
2006-03-04 21:05 ` Duncan
2006-03-04 21:47 ` Thomas de Grenier de Latour
2006-03-04 22:04 ` Simon Stelling
2006-03-04 22:28 ` Thomas de Grenier de Latour
2006-03-05 18:47 ` Mike Frysinger
2006-03-05 19:53 ` [gentoo-dev] " MIkey
2006-03-05 19:57 ` Jan Kundrát
2006-03-05 20:10 ` Mike Frysinger
2006-03-05 20:35 ` [gentoo-dev] " MIkey
2006-03-05 22:11 ` Ferris McCormick
2006-03-05 22:38 ` [gentoo-dev] " MIkey
2006-03-05 22:42 ` [gentoo-dev] " John Mylchreest
2006-03-06 0:09 ` [gentoo-dev] Re: Re: Re: Re: " Mike Frysinger
2006-03-06 16:45 ` Paul de Vrieze
2006-03-06 17:11 ` [gentoo-dev] " MIkey
2006-03-06 20:09 ` [gentoo-dev] " Paul de Vrieze
2006-03-05 22:34 ` [gentoo-dev] Re: Re: Re: Re: " Edward Catmur
2006-03-04 19:24 ` [gentoo-dev] " Ferris McCormick
2006-03-04 19:45 ` [gentoo-dev] " MIkey
2006-03-04 20:47 ` Ferris McCormick
2006-03-05 13:16 ` Patrick Börjesson
2006-03-05 14:52 ` Ned Ludd
2006-03-04 16:37 ` [gentoo-dev] " Duncan
2006-03-04 16:02 ` [gentoo-dev] " Carsten Lohrke
2006-03-06 16:49 ` Paul de Vrieze
2006-03-06 21:08 ` Carsten Lohrke
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=20060304010439.30478098@snowdrop.home \
--to=ciaranm@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