From: Peter Ruskin <aoyu93@dsl.pipex.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] *-doc vs USE="doc"
Date: Sat, 12 Jul 2003 16:22:47 +0100 [thread overview]
Message-ID: <200307121622.48112.aoyu93@dsl.pipex.com> (raw)
In-Reply-To: <1058021393.31354.65.camel@mcvaio.liquidx.net>
On Saturday 12 Jul 2003 15:49, Alastair Tse wrote:
> 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.
Sometimes the sources are different. Please see Bug #24335 for an
example of API docs and tutorials depending on the doc flag.
Peter
--
==================================================
Gentoo Linux: Gentoo Base System version 1.4.3.8p1
kernel-2.4.22_pre2-gss i686 AMD Athlon(tm) XP 1600+
==================================================
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-12 15:22 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
2003-07-12 15:22 ` Peter Ruskin [this message]
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=200307121622.48112.aoyu93@dsl.pipex.com \
--to=aoyu93@dsl.pipex.com \
--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