| 1 |
"Diego 'Flameeyes' Pettenò" <flameeyes@g.o> wrote: |
| 2 |
|
| 3 |
> Not sure if anybody here knows, but alsa-plugins is not the only set |
| 4 |
> of plugins an user installs in its system, many others are installed |
| 5 |
> by alsa-lib itself, they are the basic plugins like dmix, dsnoop, |
| 6 |
> iec958, plug... the ones that many asoundrc already make use of. |
| 7 |
> |
| 8 |
> Now of course, most of the users need them, and disabling them would |
| 9 |
> be pretty bad, but again, there are reasons to disable some of them |
| 10 |
> at least, especially when targetting small embedded devices. |
| 11 |
> |
| 12 |
> If nobody has anything against this, I'll add an ALSA_PCM_PLUGINS |
| 13 |
> variable where users can choose the plugins they want built, to |
| 14 |
> reduce the amount of code installed by alsa-lib: |
| 15 |
> |
| 16 |
> Calculating dependencies... done! |
| 17 |
> [ebuild R ] media-libs/alsa-lib-1.0.14_rc1 USE="-alisp -debug |
| 18 |
> -doc -midi" ALSA_PCM_PLUGINS="-adpcm -alaw -asym -copy -dmix -dshare |
| 19 |
> -dsnoop -empty -extplug -file -hooks iec958 -ioplug -ladspa -lfloat |
| 20 |
> -linear -meter -mulaw -multi -null plug -rate -route -share -shm |
| 21 |
> -softvol" 0 kB |
| 22 |
|
| 23 |
I don't think the average user, even the average Gentoo user, has any |
| 24 |
idea what any of these plug-ins do, how they work, and which ones they |
| 25 |
need. This is getting a bit too complicated. Is there any way to |
| 26 |
install everything as we've always done but still provide some way for |
| 27 |
embedded to do their thing? Keeping the ALSA_PCM_PLUGINS around |
| 28 |
but putting it in USE_EXPAND_HIDDEN might work. People who want the |
| 29 |
ability to turn off alsa-lib plug-ins could then do so in |
| 30 |
make.conf without confusing the hell out of everyone else. ;) |
Archives