From: "Chris Bainbridge" <chris.bainbridge@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Purpose of USE=doc
Date: Tue, 25 Apr 2006 20:08:50 +0100 [thread overview]
Message-ID: <623652d50604251208n27f718cdg9ed8eb6b6cc8f101@mail.gmail.com> (raw)
In-Reply-To: <444E6454.5040907@gentoo.org>
On 25/04/06, Jakub Moc <jakub@gentoo.org> wrote:
> Hello here,
>
> I'd like to see some clarification of intended doc use flag usage, so
> that we wouldn't force users to download/install 40+ megs of docs for a
> ~3 meg package, with the only reason being that USE=doc is for developer
> documentation only. [1]
The handbook states that "doc" is for package documentation. I've
never heard of it being restricted to developer docs only, and if
that's true, there are many packages which break that policy.
As I always understood it, "doc" is there for all optional
documentation such as manuals, APIs etc. Non-optional documentation
would be things like online docs accessible from within the program
(eg. "help" menu items for gui apps), which if missing generate
run-time errors.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-25 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 18:03 [gentoo-dev] Purpose of USE=doc Jakub Moc
2006-04-25 19:08 ` Chris Bainbridge [this message]
2006-04-26 6:43 ` Kevin F. Quinn (Gentoo)
2006-04-26 7:31 ` [gentoo-dev] " Duncan
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=623652d50604251208n27f718cdg9ed8eb6b6cc8f101@mail.gmail.com \
--to=chris.bainbridge@gmail.com \
--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