From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: sys-apps/texinfo vs @system
Date: Sun, 31 Mar 2013 12:19:28 +0200 [thread overview]
Message-ID: <20824.3504.433919.921378@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <pan$527de$b390106$9b81857f$775e3a08@cox.net>
>>>>> On Sun, 31 Mar 2013, Duncan wrote:
> Or maybe your intent was to either kill these deps or put them
> behind USE=doc as well?
USE=doc doesn't look right for this, as it's normally used for large
sized documentation. Something like USE=info might be better.
Ulrich
next prev parent reply other threads:[~2013-03-31 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 5:59 [gentoo-dev] sys-apps/texinfo vs @system Mike Frysinger
2013-03-31 9:19 ` [gentoo-dev] " Duncan
2013-03-31 10:19 ` Ulrich Mueller [this message]
2013-03-31 22:08 ` Michael Mol
2013-04-01 18:10 ` Mike Frysinger
2013-03-31 21:42 ` [gentoo-dev] " Anthony G. Basile
2013-03-31 22:07 ` Doug Goldstein
2013-03-31 22:12 ` Diego Elio Pettenò
2013-04-01 8:02 ` [gentoo-dev] " Michael Palimaka
2013-04-01 18:12 ` [gentoo-dev] " Mike Frysinger
2013-04-01 18:34 ` Rich Freeman
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=20824.3504.433919.921378@a1i15.kph.uni-mainz.de \
--to=ulm@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