From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] RFC: Local Javadoc Linking
Date: Sat, 24 Oct 2009 15:50:10 +0300 [thread overview]
Message-ID: <4AE2F802.8050904@gentoo.org> (raw)
In-Reply-To: <20091023162229.GH29871@vulcan.guest.intuitivelyobvious.net>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Daniel Solano Gómez wrote:
>
> Limitations
> -----------
>
> 1. The method above is opportunistic. If the user does not have any
> local API documentation, none is used. It is possible to modify the
> script to ensure that an ebuild's dependencies have the doc USE flag
> enabled, but that seems a bit heavy-handed to me.
>
I think we could have two use flags:
- doc: build javadoc and link to whatever is installed
- javadoc-deep: pull in all deps with [javadoc-deep?]
Better naming suggestions for the second use flag are welcome.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2009-10-24 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 16:22 [gentoo-java] RFC: Local Javadoc Linking Daniel Solano Gómez
2009-10-24 10:06 ` Hanno Meyer-Thurow
2009-10-24 12:50 ` Petteri Räty [this message]
2009-10-24 14:34 ` Hanno Meyer-Thurow
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=4AE2F802.8050904@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-java@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