From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Default useflag cleanups: -apm -foomaticdb -fortran -imlib -motif -oss -xmms
Date: Tue, 6 Jun 2006 08:40:44 +0200 [thread overview]
Message-ID: <20060606084044.39a80562@eusebe> (raw)
In-Reply-To: <1149557038.25202.5.camel@vertigo.twi-31o2.org>
On Mon, 05 Jun 2006 21:23:58 -0400,
Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> There are *many* applications in the tree that do not use ALSA, but
> work only via the OSS emulation. Removing this is a bad idea and it
> would definitely be blocked by the games team. Probably half of the
> packages that I maintain require OSS capabilities.
I think the problem is that the "oss" flag is used for (at least) two
slighlty different things:
- in alsa-driver, it adds OSS capabilities. That's something most
people want, and should be enable by default.
- in most (all?) other packages, it enables optionnal OSS output.
That's something most people don't use and don't wan't enabled by
default.
Imho, when there is no "good" global value for a flag, it means it
shouldn't be a single global flag (at least, until there is some
kind of per-package defaults support in Portage). So, what about a
local "oss-emulation" flag instead in alsa-drivers, which would be the
only one turned on in profiles? Wouldn't it makes everyone happy?
--
TGL.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-06 6:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 16:03 [gentoo-dev] Default useflag cleanups: -apm -foomaticdb -fortran -imlib -motif -oss -xmms Stefan Schweizer
2006-06-05 16:16 ` Patrick McLean
2006-06-06 3:58 ` Mike Frysinger
2006-06-05 16:16 ` Grant Goodyear
2006-06-05 16:33 ` Harald van Dijk
2006-06-05 16:59 ` Carsten Lohrke
2006-06-05 18:08 ` Harald van Dijk
2006-06-05 19:45 ` Carsten Lohrke
2006-06-06 2:45 ` Andrew Muraco
2006-06-06 9:16 ` Carsten Lohrke
2006-06-05 18:36 ` George Shapovalov
2006-06-05 18:52 ` Chris Gianelloni
2006-06-05 19:57 ` Carsten Lohrke
2006-06-05 21:25 ` Chris Gianelloni
2006-06-05 22:18 ` Carsten Lohrke
2006-06-05 19:22 ` Wernfried Haas
2006-06-05 19:58 ` Luis Medinas
2006-06-05 20:50 ` Wernfried Haas
2006-06-08 8:30 ` Robin H. Johnson
2006-06-08 10:30 ` Luis Medinas
2006-06-08 10:15 ` Mike Frysinger
2006-06-06 1:23 ` Chris Gianelloni
2006-06-06 2:10 ` [gentoo-dev] " Stefan Schweizer
2006-06-06 2:31 ` Chris Gianelloni
2006-06-06 6:47 ` Doug Goldstein
2006-06-06 14:38 ` Mike Doty
2006-06-06 2:11 ` Michael Sterrett -Mr. Bones.-
2006-06-06 9:19 ` Carsten Lohrke
2006-06-06 4:07 ` [gentoo-dev] " Mike Frysinger
2006-06-06 5:31 ` Harald van Dijk
2006-06-06 5:48 ` Mike Frysinger
2006-06-06 6:13 ` Harald van Dijk
2006-06-06 6:34 ` John Myers
2006-06-06 9:26 ` Diego 'Flameeyes' Pettenò
2006-06-07 9:42 ` Mike Frysinger
2006-06-06 9:17 ` Carsten Lohrke
2006-06-06 9:25 ` Diego 'Flameeyes' Pettenò
2006-06-06 10:14 ` Carsten Lohrke
2006-06-06 15:43 ` Chris Gianelloni
2006-06-06 6:40 ` Thomas de Grenier de Latour [this message]
2006-06-06 15:44 ` Chris Gianelloni
2006-06-06 4:00 ` Mike Frysinger
2006-06-06 6:51 ` Doug Goldstein
2006-06-06 16:24 ` Jason Wever
2006-06-06 23:05 ` Danny van Dyk
2006-06-07 0:37 ` Chris Gianelloni
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=20060606084044.39a80562@eusebe \
--to=degrenier@easyconnect.fr \
--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