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: Mon, 14 Nov 2016 16:44:03 +0200 [thread overview]
Message-ID: <1479134643.1949.3.camel@iki.fi> (raw)
In-Reply-To: <s5hoa1i2vo0.wl-tiwai@suse.de>
On Mon, 2016-11-14 at 11:38 +0100, Takashi Iwai wrote:
> On Wed, 09 Nov 2016 15:39:26 +0100,
> Tanu Kaskinen wrote:
> >
> > 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?
>
> Actually, I was wrong. Even sbase.so isn't needed for the normal
> alsamixer / amixer operations. This is a base shared object that is
> needed for "basic" abstraction mode, but the normal mode (abstraction
> "none") doesn't need it.
>
> That said, the whole /usr/lib*/alsa-lib/smixer/* stuff can be removed
> from your package as long as the normal mode is used.
>
> There is an option -a to pass the abstraction level. When you pass
> "basic", the python module gets loaded. It was supposed to handle the
> card-specific abstraction parsed via python, but this seems currently
> broken. So it's maybe safer to disable as default...
Ok, thanks for the update! I see you submitted a patch that disables
these plugins if Python is disabled. OpenEmbedded builds alsa-lib
without Python support, so I guess these plugins won't be available to
OpenEmbedded users starting from alsa-lib 1.1.3. For now there's
nothing I need to change in the packaging.
--
Tanu
https://www.patreon.com/tanuk
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-11-14 14:44 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
2016-11-14 10:38 ` Takashi Iwai
2016-11-14 14:44 ` Tanu Kaskinen [this message]
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=1479134643.1949.3.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).