From: Jakub Moc <jakub@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Purpose of USE=doc
Date: Tue, 25 Apr 2006 20:03:00 +0200 [thread overview]
Message-ID: <444E6454.5040907@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
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]
And no, I don't think we need yet another use flag. ;) FEATURES="nodoc"
is also not exactly useful as it's forcing users to download stuff they
are not interested in at all. (To make it more clear, I'm talking about
ebuilds that download docs in a separate tarball here.)
TIA for ideas.
[1] http://bugs.gentoo.org/show_bug.cgi?id=122265
--
Best regards,
Jakub Moc
mailto:jakub@gentoo.org
GPG signature:
http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E
... still no signature ;)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-04-25 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 18:03 Jakub Moc [this message]
2006-04-25 19:08 ` [gentoo-dev] Purpose of USE=doc Chris Bainbridge
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=444E6454.5040907@gentoo.org \
--to=jakub@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