public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] We have "doc" USE flag, why not a "man" USE flag too
Date: Wed, 10 Aug 2005 16:31:46 +0100	[thread overview]
Message-ID: <20050810163146.56512462@snowdrop.home> (raw)
In-Reply-To: <200508110024.57048.jstubbs@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Thu, 11 Aug 2005 00:24:54 +0900 Jason Stubbs <jstubbs@gentoo.org>
wrote:
| On Wednesday 10 August 2005 22:19, Ciaran McCreesh wrote:
| > On Wed, 10 Aug 2005 09:10:39 -0400 Michael Cummings
| >
| > <mcummings@gentoo.org> wrote:
| > | (not directed at dsd in particular, just the last one in my inbox
| > | to reply :) That's great and all that its in features for the
| > | installation, but what about packages with optional dependencies
| > | based on doc and man?
| >
| > Join in the quest to get FEATURES added to the expand list! Bug
| > #82513.
| 
| Personally, I think adding FEATURES to USE_EXPAND is terrible.
| Portage features are not ebuild features. How much do you like C code
| that has #ifdef's for the compiler being used? It's the same thing.

Then please introduce TESTDEPEND, MANDEPEND and INFODEPEND instead.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-10 15:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 12:09 [gentoo-dev] We have "doc" USE flag, why not a "man" USE flag too Bjarke Istrup Pedersen
2005-08-10 12:16 ` Jakub Moc
2005-08-10 12:19 ` Diego 'Flameeyes' Pettenò
2005-08-10 12:20 ` Daniel Drake
2005-08-10 13:10   ` Michael Cummings
2005-08-10 13:16     ` Mike Frysinger
2005-08-10 15:14       ` Diego 'Flameeyes' Pettenò
2005-08-10 15:57         ` Georgi Georgiev
2005-08-10 13:19     ` Ciaran McCreesh
2005-08-10 14:58       ` Mike Frysinger
2005-08-10 15:24       ` Jason Stubbs
2005-08-10 15:31         ` Ciaran McCreesh [this message]
2005-08-10 16:06           ` Carsten Lohrke
2005-08-10 16:16             ` Ciaran McCreesh
2005-08-10 16:19             ` Diego 'Flameeyes' Pettenò
2005-08-10 17:07               ` Carsten Lohrke
2005-08-10 17:26                 ` Mike Frysinger
2005-08-10 17:38                   ` Henrik Brix Andersen
2005-08-10 18:13                   ` Carsten Lohrke
2005-08-10 18:22                     ` Mike Frysinger
2005-08-10 17:45                 ` Ciaran McCreesh
2005-08-10 18:25                   ` Carsten Lohrke
2005-08-10 18:33                     ` Mike Frysinger
2005-08-10 18:35                     ` Ciaran McCreesh
2005-08-10 18:54                       ` Carsten Lohrke
2005-08-10 19:04                         ` Ciaran McCreesh
2005-08-10 19:29                           ` Carsten Lohrke
2005-08-10 20:01                             ` Mike Frysinger
2005-08-10 23:59           ` Jason Stubbs
2005-08-10 15:34         ` Simon Stelling
2005-08-10 15:39         ` Mike Frysinger
2005-08-10 23:56           ` Jason Stubbs
2005-08-11  0:04             ` Mike Frysinger
2005-08-11 11:02               ` Jason Stubbs
2005-08-11 12:26                 ` Mike Frysinger
2005-08-11 13:40                   ` Marius Mauch
2005-08-11 14:03                     ` Mike Frysinger
2005-08-11 15:33                       ` Marius Mauch
2005-08-12  1:16                   ` Jason Stubbs
2005-08-10 13:22     ` Diego 'Flameeyes' Pettenò

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=20050810163146.56512462@snowdrop.home \
    --to=ciaranm@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