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