alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Tanu Kaskinen <tanuk@iki.fi>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: How to package the smixer modules?
Date: Wed, 09 Nov 2016 16:39:26 +0200	[thread overview]
Message-ID: <1478702366.1952.1.camel@iki.fi> (raw)
In-Reply-To: <s5hlgwu9gtx.wl-tiwai@suse.de>

On Tue, 2016-11-08 at 15:39 +0100, Takashi Iwai wrote:
> The simple mixer is another layer in ALSA mixer API, and actually it's
> mandatory.  So, at least, sbase plugin should be provided always when
> alsa-lib mixer API is used.  Other plugins are basically never used
> practically.
> 
> It doesn't matter whether to package them separately or not.  The only
> point is that sbase plugin should be available when alsa-lib mixer API
> is used.

Thanks for the explanation! If the sbase plugin is essentially a
mandatory accompaniment of libasound, I'll move it to the libasound
package, and since I don't see much benefit in keeping the hda and ac97
plugins in a separate package either, I'll move those too and get rid
of the whole smixer plugin package.

Out of curiosity, in what situation are the hda and ac97 plugins used?
You said that they are practically never used, but surely they have
some purpose?

-- 
Tanu

https://www.patreon.com/tanuk

  reply	other threads:[~2016-11-09 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 12:43 How to package the smixer modules? Tanu Kaskinen
2016-11-08 14:39 ` Takashi Iwai
2016-11-09 14:39   ` Tanu Kaskinen [this message]
2016-11-14 10:38     ` Takashi Iwai
2016-11-14 14:44       ` Tanu Kaskinen
2016-11-14 15:22         ` Takashi Iwai

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=1478702366.1952.1.camel@iki.fi \
    --to=tanuk@iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).