public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] oss in make.defaults for 2006.0?
Date: Fri, 25 Nov 2005 09:21:33 -0500	[thread overview]
Message-ID: <1132928493.19957.24.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <1132927534.8482.2.camel@Darkmere.darkmere>

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

On Fri, 2005-11-25 at 15:05 +0100, Spider (D.m.D. Lj.) wrote:
> On Fri, 2005-11-25 at 11:00 +0100, Michiel de Bruijne wrote:
> > On Friday 25 November 2005 10:24, Luca Barbato wrote:
> > > Michiel de Bruijne wrote:
> > > > Now that useflags are evaluated for the 2006.0 profile (e.g. nptl and
> > > > apache2) I wonder if it's still necessary to have oss in make.defaults?
> > > > The replacement (alsa) is preferred by kernel developers for almost 2
> > > > years. Time to remove it from the 2006.0 profile?

Never... going... to... happen... (don't worry, I'll explain)

> > > I'd have a look at how many software are using oss only and how many
> > > have good alsa support, not to mention which drivers are oss only or
> > > work better as oss.

The software that primarily supports OSS only is my other area in
Gentoo... games.

There's no way that we can make, for example, Return to Castle
Wolfenstein or Enemy Territory, both of which are extremely popular, use
ALSA natively.  They *do* work with ALSA compiled with USE="oss" or with
alsa-oss installed.  As far as I know, the oss USE flag on ALSA only
enables the alsa-oss dependency.

> Theres a few issues here, at least Trident and via chipsets work good in
> alsa. however, due to the difficulty for programmers to use the
> alsa-api, you actually get -better- sound (less glitches and buffer
> underruns) if you use alsa-drivers + alsa-oss emulation.
> 
> This is clearly visible in Fex.  amarok (gstreamer backend) and other
> players, especially under higher system loads. (yes, even with a
> preemptive kernel)
> 
> 
> 
> > For the programs that are oss-only a useflag shouldn't even exists, because 
> > it's not optional.

For those applications, correct.  However, I have shown a good reason
for it.  Unless we simply tell anyone to always merge alsa-oss if they
want to play games, which isn't exactly a "works out of the box"
solution.  I can think of a few scenarios we could employ to work around
this, but they aren't nearly as clean as simply having OSS in the
default USE.  Personally, I think it should stay until it is removed
from the kernel, and even then, it must stay so long as we are
supporting 2.4 kernels which do not have ALSA, such as vanilla-sources.

> > All systems I maintain (about 15 different hardware/software specs) have -oss 
> > and work as expected. I'm interested if someone on this list has 
> > hardware/software where oss is preferred over alsa?
> > Does anybody knows if the default setup of other distros include 
> > "oss-compiled" packages?
> 
> Yeah, they do. At least last I checked both ubuntu and Fedora Core had
> oss as their default sound-sinks for many things. The transition period
> will take ages I'm afraid :/

I would say a very long time, indeed.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-11-25 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-25  9:14 [gentoo-releng] oss in make.defaults for 2006.0? Michiel de Bruijne
2005-11-25  9:24 ` Luca Barbato
2005-11-25 10:00   ` Michiel de Bruijne
2005-11-25 14:05     ` Spider (D.m.D. Lj.)
2005-11-25 14:21       ` Chris Gianelloni [this message]
2005-11-26  8:32         ` Michiel de Bruijne
2005-11-26 23:28           ` Chris Gianelloni
2005-11-27 22:32             ` Spider (D.m.D. Lj.)

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=1132928493.19957.24.camel@vertigo.twi-31o2.org \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-releng@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