1 |
On Wed, 2007-01-24 at 01:30 +0100, Diego 'Flameeyes' Pettenò wrote: |
2 |
> As per summary. |
3 |
> |
4 |
> I've introduced th emidi useflag for alsa-lib and alsa-utils in the recent |
5 |
> versions of ALSA to enable/disable sequencer (MIDI) support, as most of home |
6 |
> users probably wouldn't need it. Unfortunately the version of alsa-lib where |
7 |
> midi can be disabled is still masked because there are packages that needs to |
8 |
> be fixed not to die badly when it is disabled (for instance KMix does not |
9 |
> complete configure because the whole ALSA test is using snd_seq_open |
10 |
> function); also, some packages might require midi support with alsa useflag |
11 |
> enabled (kdelibs for instance). |
12 |
> |
13 |
> For these reasons I'd like to maintain the default out of the box behaviour |
14 |
> consistent with the one we had before the introduction of midi useflag, |
15 |
> leaving the users the choice to disable it entirely or partially (see bug |
16 |
> #163531, where an user requested for alsa-driver to have a midi useflag |
17 |
> too -- to avoid building MIDI support in ALSA kernel drivers too). |
18 |
> |
19 |
> If nobody disagrees with this, I'll be adding midi useflag to default USE in |
20 |
> base in three days. |
21 |
|
22 |
Does it need to go in base? (I'm asking, not saying it doesn't.) |
23 |
|
24 |
Can somewhere else be more appropriate? default-linux? Basically, does |
25 |
this need to affect hardened/embedded, too, or is default-* enough? |
26 |
|
27 |
I would think that so long as this doesn't cause extra dependencies to |
28 |
be pulled into the other projects (which is sounds like it won't) then |
29 |
base should be fine. |
30 |
|
31 |
-- |
32 |
Chris Gianelloni |
33 |
Release Engineering Strategic Lead |
34 |
Alpha/AMD64/x86 Architecture Teams |
35 |
Games Developer/Council Member/Foundation Trustee |
36 |
Gentoo Foundation |