1 |
Diego 'Flameeyes' Pettenò wrote: |
2 |
> Not sure if anybody here knows, but alsa-plugins is not the only set of |
3 |
> plugins an user installs in its system, many others are installed by alsa-lib |
4 |
> itself, they are the basic plugins like dmix, dsnoop, iec958, plug... the |
5 |
> ones that many asoundrc already make use of. |
6 |
> |
7 |
> Now of course, most of the users need them, and disabling them would be pretty |
8 |
> bad, but again, there are reasons to disable some of them at least, |
9 |
> especially when targetting small embedded devices. |
10 |
> |
11 |
> If nobody has anything against this, I'll add an ALSA_PCM_PLUGINS variable |
12 |
> where users can choose the plugins they want built, to reduce the amount of |
13 |
> code installed by alsa-lib: |
14 |
> |
15 |
> Calculating dependencies... done! |
16 |
> [ebuild R ] media-libs/alsa-lib-1.0.14_rc1 USE="-alisp -debug -doc -midi" |
17 |
> ALSA_PCM_PLUGINS="-adpcm -alaw -asym -copy -dmix -dshare -dsnoop -empty -extplug -file -hooks |
18 |
> iec958 -ioplug -ladspa -lfloat -linear -meter -mulaw -multi -null |
19 |
> plug -rate -route -share -shm -softvol" 0 kB |
20 |
|
21 |
Since I'm not very alsa litterate, on a "typical" system, what kind of |
22 |
plugins - other than dmix and dsnoop - are used by "typical" |
23 |
applications (totem, mplayer, amarok, ...)? If a user decides to remove |
24 |
some plugins, do "typical" applications handle this cleanly or do they |
25 |
crash and burn? |
26 |
|
27 |
Other than that, sounds like a neat idea :) |
28 |
|
29 |
Rémi |
30 |
|
31 |
-- |
32 |
gentoo-dev@g.o mailing list |