public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ieee1394 useflag
Date: Thu, 21 Apr 2005 20:37:53 -0700	[thread overview]
Message-ID: <20050422033753.GA2212@phaenix.haell.com> (raw)
In-Reply-To: <20050421233822.GA27292@ols-dell.iic.hokudai.ac.jp>

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

At 2005-04-22T08:38:22+0900, Georgi Georgiev <chutz@gg3.net> wrote:
> maillog: 21/04/2005-23:43:57(+0200): Diego 'Flameeyes' Petten? types
> > Same for ieee1394, usually enables support for
> > media-plugins/libdc1394, sys-libs/libavc1394 and/or
> > sys-libs/libraw1394.
> 
> Considering that a person rarely needs *both* libdc1394 and
> libavc1394, it would be even cooler to have *two* useflags.

Generally, I've noticed that use flags are named for the functionality
they enable, rather than the libraries that they pull in as depends. It
might be a cleaner approach to use "ieee1394" or even just "1394" as the
global flag, and then if any future packages offer a choice between
libs, add some local flags as appropriate.

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

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

      parent reply	other threads:[~2005-04-22  3:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 21:16 [gentoo-dev] ieee1394 useflag Diego 'Flameeyes' Pettenò
2005-04-21 21:29 ` Greg KH
2005-04-21 21:43   ` Diego 'Flameeyes' Pettenò
2005-04-21 23:38     ` Georgi Georgiev
2005-04-21 23:50       ` Diego 'Flameeyes' Pettenò
2005-04-22  3:37       ` Drake Wyrm [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=20050422033753.GA2212@phaenix.haell.com \
    --to=wyrm@haell.com \
    --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