From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Unifying the behavior of the doc use flag and document it
Date: Sat, 23 Jun 2007 16:29:42 +0200 [thread overview]
Message-ID: <20070623162942.74635a1d@sheridan.genone.homeip.net> (raw)
In-Reply-To: <467D2A04.6080504@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
On Sat, 23 Jun 2007 17:11:16 +0300
Petteri Räty <betelgeuse@gentoo.org> wrote:
> My opinion is to make it clear that the doc use flag always controls
> whether or not to install documentation and make it clear in the
> devmanual. For what gnome does, they can then add for example a
> gtk-doc use flag to control the building of the cross references and
> have the doc use flag control the installation of the bundled
> documentation.
>
> betelgeuse@pena ~ $ euse -i doc
> global use flags (searching: doc)
> ************************************************************
> [- ] doc - Adds extra documentation (API, Javadoc, etc)
>
> INSTALL_MASK is of course a solution to not installing gtk-doc at all
> but it doesn't give me the ability to install it only for individual
> packages.
>
> What do others think?
Maybe the flag needs to be renamed/split up to clarify it's meaning,
it's too generic in it's current form (many people enable it blindly and
don't really have any clue what the result is).
Like using USE=apidoc for API documentation, USE=extradoc for extra
user documentation (controlling PDF generation and stuff like that),
USE=rebuild-docs to replace pregenerated documentation with
updated/regenerated versions (like the gtk-doc issue), and so on (don't
know what other use cases there are for USE=doc currently).
It's a large change, but USE=doc has been a significant problem for
quite a while already (circular deps anyone?)
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-23 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 14:11 [gentoo-dev] RFC: Unifying the behavior of the doc use flag and document it Petteri Räty
2007-06-23 14:19 ` Ciaran McCreesh
2007-06-23 14:45 ` Petteri Räty
2007-06-23 14:57 ` Ciaran McCreesh
2007-06-23 16:27 ` Mart Raudsepp
2007-06-25 1:58 ` Daniel Drake
2007-06-23 14:29 ` Marius Mauch [this message]
2007-06-23 14:34 ` Petteri Räty
2007-06-24 12:46 ` [gentoo-dev] " Steve Long
2007-06-24 13:42 ` Kent Fredric
2007-06-24 13:47 ` Ciaran McCreesh
2007-06-24 20:50 ` [gentoo-dev] " Steve Long
2007-06-25 14:07 ` Steve Long
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=20070623162942.74635a1d@sheridan.genone.homeip.net \
--to=genone@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