From: Spider <spider@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New global USE flag: examples
Date: Sun, 22 Aug 2004 05:44:31 +0200 [thread overview]
Message-ID: <20040822054431.28a857bc.spider@gentoo.org> (raw)
In-Reply-To: <20040822023438.GS28058@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
begin quote
On Sun, 22 Aug 2004 04:34:38 +0200
Karl Trygve Kalleberg <karltk@gentoo.org> wrote:
>
> In java, we have many libraries that are a few hundred kb, that come
> with multiple megabytes of generated documentation, that you will only
> need if you're a Java developer, and usually not even then.
> Also, as javadoc is a memory hog, generating the documentation may be
> prohibitive on older machines.
Actually, you just describe the reason we implemented the "doc" useflag.
Its not meant for enduser documentation in that sense, but for more
massive, developer oriented documentation that is autogenerated in some
ways. okay, its misnamed, I realized that afterwards, too late.
it was basically there to stop packages from pulling in t1, tetex,
openjade, ghostscript and the rest, just to parse some .h headers with a
perl script and generate documentation in multitudes of formats.
So, the documentation / javadoc, are best off covered by the USE="doc"
flag, whereas examples should probably be split up a bit further.
(examplecode !)
Its fairly important that we don't start to misuse such a flag for
example configurations, which should be considered necessary base level
documentation for users, not "examples" in the sense we are talking
about here.
(for a typical "example" app, freepascal is an example ;)
//Spider
--
begin .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-22 3:44 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 [this message]
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
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=20040822054431.28a857bc.spider@gentoo.org \
--to=spider@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