From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: RFC: Unifying the behavior of the doc use flag and document it
Date: Sun, 24 Jun 2007 21:50:46 +0100 [thread overview]
Message-ID: <f5mlfb$gub$1@sea.gmane.org> (raw)
In-Reply-To: 8cd1ed20706240642l23d9db05g430758fcbc6c6c60@mail.gmail.com
Kent Fredric wrote:
>> ++ I was only thinking of the programmer:user difference, since code docs
>> tend to pull in a lot of stuff, where as end-user docs are normally
>> supplied in an easier format (eg not dox ;) rebuild-docs as a one-shot
>> flag is great.
>>
>> Would there be a way to control what kind of markup is output (assuming a
>> package supports it)? For example, to specify that files should be for
>> text-only or graphical browser (where both would be the default.) XeTeX
>> -- PS -- PDF is another along those lines.
>
> I can just feel a USE expansion coming on.
>
> DOC="none pdf txt man ps html info all rebuild" sounds like just a
> bunch for starters.
>
> Any votees?
>
Not me, I'm afraid, unless this is the only way to do it.. I agree that they
should only apply to single packages, not across the tree. Although, if I'm
honest, I don't know what that breaks.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-24 21:02 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
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 ` Steve Long [this message]
2007-06-25 14:07 ` [gentoo-dev] " 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='f5mlfb$gub$1@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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