public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Mylchreest <johnm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-core] Re: [gentoo-dev] Possible virtual/alsa change
Date: Thu, 27 Oct 2005 19:37:37 +0100	[thread overview]
Message-ID: <1130438257.10014.38.camel@localhost> (raw)
In-Reply-To: <43611C4F.6070703@gentoo.org>

On Thu, 2005-10-27 at 14:28 -0400, Stephen P. Becker wrote:
> The problem is that *all* mips-sources ebuilds do not provide alsa. 
> Only the mips-sources-2.6.* versions do this, and then only if 
> USE="ip30" (Octane users).

This makes sense, although not the USE flag.

> I'm just worried about folks running 2.4 systems (only Indys at this 
> point) with mips-sources "providing" alsa, but not really.  This could 
> get even more tricky because I happen to know somebody is working on an 
> alsa driver for Indy, and it will be for 2.6 only.  We're trying really 
> hard to get everything to where we can just get rid of 2.4, but until 
> that time, setting the virtual to mips-sources is technically broken.

Of course, 2.4 kernels are technically broken because they dont support
alsa, and this is fixed in other profiles with the inclusion of a 2.4
(or 2.6) sub profile. However.. if nothing actually works with alsa,
then I dont see the problem in that case of making the profile default
mips-sources. if it happens to install 2.4 sources, then so be it. it
might be a technically incorrect provide.. but nothing else can fill it
any better. At least at this moment in time.

If it were me, thats what I would do. But of course, this change doesn't
really make any difference to mips one way or the other.

-- 
Role:            Gentoo Linux Kernel Lead
Gentoo Linux:    http://www.gentoo.org
Public Key:      gpg --recv-keys 9C745515     
Key fingerprint: A0AF F3C8 D699 A05A EC5C  24F7 95AA 241D 9C74 5515
Web:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9C745515

-- 
gentoo-dev@gentoo.org mailing list



      reply	other threads:[~2005-10-27 18:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 18:25 [gentoo-dev] Possible virtual/alsa change Chris Gianelloni
2005-10-17 18:42 ` Diego 'Flameeyes' Pettenò
2005-10-17 19:08   ` Jan Kundrát
2005-10-24 10:50     ` Shyam Mani
2005-10-24 13:11       ` Chris Gianelloni
2005-10-24 13:18         ` [gentoo-core] " Stephen P. Becker
2005-10-24 13:30           ` Chris Gianelloni
2005-10-24 13:56             ` Stephen P. Becker
2005-10-24 14:54               ` Chris Gianelloni
2005-10-24 15:03                 ` Stephen P. Becker
2005-10-24 15:21                   ` Chris Gianelloni
2005-10-24 19:41                     ` Stephen P. Becker
2005-10-24 19:25                       ` Ciaran McCreesh
2005-10-25  2:22                       ` Chris Gianelloni
2005-10-27 18:13                       ` John Mylchreest
2005-10-27 18:28                         ` Stephen P. Becker
2005-10-27 18:37                           ` John Mylchreest [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=1130438257.10014.38.camel@localhost \
    --to=johnm@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