From: Uwe Thiem <uwix@iway.na>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kdelibs / API doc
Date: Tue, 15 Aug 2006 16:15:16 +0100 [thread overview]
Message-ID: <200608151615.17159.uwix@iway.na> (raw)
In-Reply-To: <1155652202.827.3.camel@gentoo>
On 15 August 2006 15:30, Alan Mckinnon wrote:
> On Tue, 2006-08-15 at 12:32 +0100, Uwe Thiem wrote:
> > Hi folks,
> >
> > I emerge kdedelibs with the "doc" USEFLAG but can't find the
> > documentation anywhere. It did work with qt. What am I missing?
> >
> > Of course, I could unpack the kdelibs tarball in my home directory and
> > create the documentation manually, but isn"t there an automatic way of
> > doing it?
>
> The doc flag works for me. From the ebuild:
>
> DEPEND="${RDEPEND}
> doc? ( app-doc/doxygen )
> ...
>
> Which installed a ton of stuff in /usr/kde/3.5/share/doc/HTML/en/
Thank you!
Uwe
(blind, deaf ... and illiterate)
--
Mark Twain: I rather decline two drinks than a German adjective.
http://www.SysEx.com.na
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-08-15 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 11:32 [gentoo-user] kdelibs / API doc Uwe Thiem
2006-08-15 14:30 ` Alan Mckinnon
2006-08-15 15:15 ` Uwe Thiem [this message]
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=200608151615.17159.uwix@iway.na \
--to=uwix@iway.na \
--cc=gentoo-user@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