From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] 2.6.0 kernel and alsa-driver
Date: Sun, 28 Sep 2003 06:51:01 +0200 [thread overview]
Message-ID: <20030928065101.2cbfe6e5.genone@gentoo.org> (raw)
In-Reply-To: <200309281146.50059.jasonbstubbs@mailandnews.com>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On 09/28/03 Jason Stubbs wrote:
> Hello all,
>
> There is a discepancy in the way that mm-sources and
> development-sources handles virtual/alsa. Have a look:
>
> bash-2.05b$ grep alsa /usr/portage/sys-kernel/development-sources/
> development-sources-2.6.0_beta5-r11.ebuild
> IUSE="alsa"
> [ -n "$(use alsa)" ] && PROVIDE="${PROVIDE} virtual/alsa"
>
> bash-2.05b$ grep alsa /usr/portage/sys-kernel/mm-sources/
> mm-sources-2.6.0_beta5-r4.ebuild
> virtual/alsa"
>
> In other words, development-sources will provide virtual/alsa only if
> the use flag is set when it is emerged. mm-sources, however, will
> provide virtual/ alsa regardless. Which is the correct behaviour?
>
> Personally, I think mm-sources is the better option. The reason being
> if a user decides to use alsa after emerging development-sources by
> adding alsa to the use flags, portage will see no virtual/alsa and try
> and pull in alsa-driver.
>
> Any opinions before I post a bug?
PROVIDE should not be conditional and it doesn't even make sense in this
case as the kernel has alsa modules independent of the alsa USE flag. So
file a bug for development sources.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-28 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 2:46 [gentoo-dev] 2.6.0 kernel and alsa-driver Jason Stubbs
2003-09-28 4:51 ` Marius Mauch [this message]
2003-09-28 9:29 ` Jason Stubbs
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=20030928065101.2cbfe6e5.genone@gentoo.org \
--to=genone@gentoo.org \
--cc=gentoo-dev@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