From: Alastair Tse <liquidx@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] *-doc vs USE="doc"
Date: 12 Jul 2003 15:49:55 +0100 [thread overview]
Message-ID: <1058021393.31354.65.camel@mcvaio.liquidx.net> (raw)
In-Reply-To: <20030712122508.33796f7d.spider@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]
On Sat, 2003-07-12 at 11:25, Spider wrote:
> Well, this is an no-issue issue, from the beginning doc was used to
> differentiate wether to build the (costly, dependencywise and timewise)
> .ps, pdf. html and other versions of documentation from the original
> templates, actions which required jade, tetex and a lot of cpupower, or
> wether to just install the basic pregenerated documentation.
>
> This too goes for source-included things like gtk-doc (library
> documentation)
>
> So, any case that uses "doc" to differentiate manpages or general
>
OK, so "doc" is only to separate developer documentation? Is that a fair
definition? If so then I think the description of the useflag should be
modified. Because right now, it is very vague saying "Add Extra
Documentation".
> To separate devleoper-documentation is a common thing to do, since API's
> tend to change less frequently, so for say java 1.2.* could well use
> the documentation from any java-1.2 standard + some errata
>
> I'd suggest marking all packages that separate end-user documentation
> with USE="doc" are flawed and should be fixed. All those who have extra
> developer-centric documentation (api, examples and so on) could well
> have them separated in RDEPEND="doc? (${PN}-api-documentation )"
That seems reasonable. I just want clarify how we should handle docs. I
guess this is acceptable way. Just wondering why the docs aren't
actually included in the package themselves.
Cheers,
--
Alastair 'liquidx' Tse
>> Gentoo Developer
>> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/
>> GPG Key : http://dev.gentoo.org/~liquidx/liquidx_gentoo_org.asc
>> FingerPrint : 579A 9B0E 43E8 0E40 EE93 BB1C 38CE 1C7B 3907 14F6
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-12 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 8:42 [gentoo-dev] *-doc vs USE="doc" Alastair Tse
2003-07-12 10:25 ` Spider
2003-07-12 14:49 ` Alastair Tse [this message]
2003-07-12 15:22 ` Peter Ruskin
2003-07-12 11:53 ` Mamoru KOMACHI
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=1058021393.31354.65.camel@mcvaio.liquidx.net \
--to=liquidx@gentoo.org \
--cc=gentoo-dev@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