public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthieu Sozeau <mattam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New global USE flag: examples
Date: Mon, 23 Aug 2004 17:39:41 +0200	[thread overview]
Message-ID: <200408231739.48676.mattam@gentoo.org> (raw)
In-Reply-To: <200408231036.47562.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

On Monday 23 August 2004 16:36, Mike Frysinger wrote:
> On Monday 23 August 2004 08:30 am, Paul de Vrieze wrote:
> > I disagree with you. Documentation is very different from example
> > applications and the like. The java herd is not the only group having
> > problems with this. Look for example at the formidable example collection
> > provided in qt. In most cases it is not necessary at all to compile them
> > all (take quite some time), while developer docs might be interesting.
>
> doc works fine if you consider the context ...
>
> USE=doc [some programming language] -> i get a lot of programming related
> documentation
USE="doc examples" [some programming language] -> i get the language ref 
manual and library docs + some example programs if provided.

> USE=doc [some program] -> i get a lot of manuals and extraneous things
USE="doc examples" [some program] -> i get a lot of manuals and some sample 
documents (could be used in Dia for example).

USE=doc [some library] -> i get the API docs
USE="doc examples" -> ^^^ + example code/apps

You seem to see it too fine-grained, but there are people who want API docs 
but not example code (I am a living example). USE flags are about 
flexibility, aren't they ? Micheal says there is no need, that's true, but 
some people wish this USE flag existed so they could have more control on 
what's installed.
-- 
"We have art to save ourselves from the truth." 
- Friedrich Nietzsche

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-08-23 15:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21 19:37 [gentoo-dev] New global USE flag: examples Matthieu Sozeau
2004-08-21 19:46 ` Norberto Bensa
2004-08-21 19:52   ` Ciaran McCreesh
2004-08-21 20:15     ` Norberto Bensa
2004-08-21 20:28       ` Ciaran McCreesh
2004-08-23 12:25         ` Paul de Vrieze
2004-08-21 22:43       ` Stroller
2004-08-23 12:23     ` Paul de Vrieze
2004-08-23 14:34       ` Tuan Van
2004-08-21 19:48 ` Ciaran McCreesh
2004-08-21 19:59   ` Carsten Lohrke
2004-08-21 20:11   ` Matthieu Sozeau
2004-08-22  0:27 ` Karl Trygve Kalleberg
2004-08-22  0:52   ` Michael Sterrett -Mr. Bones.-
2004-08-22  2:34     ` Karl Trygve Kalleberg
2004-08-22  3:44       ` Spider
2004-08-22  6:52         ` Mike Frysinger
2004-08-22 13:45 ` Matthieu Sozeau
2004-08-22 19:12   ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2004-08-22 23:28     ` Matthieu Sozeau
2004-08-23 12:30     ` Paul de Vrieze
2004-08-23 14:36       ` Mike Frysinger
2004-08-23 15:39         ` Matthieu Sozeau [this message]

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=200408231739.48676.mattam@gentoo.org \
    --to=mattam@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