2012/1/27 Paul Eggleton <[email protected]>: > On Friday 27 January 2012 11:43:50 Samuel Stirtzel wrote: >> just a quick question, couldn't we use a separate recipe for phonon, >> so if a recipe depends on it we don't have to change distro vars? > > Well, this thread is now about something more fundamental (how to introduce > new DISTRO_FEATURES), but we do still need to solve the problem that prompted > the wider discussion. It's still possible that someone would want to build > phonon without pulseaudio, even if it was split out into a separate recipe, so > I'm not sure that addresses the problem.
Oh ok, I thought just about Qt + Phonon +- Pulseaudio case. If a user disables or enables Pulseaudio he would need to rebuild all Qt stuff to make it work (and building Qt is time consuming). With a separate phonon recipe he could just rebuild the libphonon recipe instead. > >> IMHO it would be easier to just depend on libphonon.bb instead of >> adding a distro var for the one single recipe I'm working on. >> Just my 0.02 cents. > > Pulseaudio has become an optional dependency for a lot of things. I think it > makes sense to make a decision on whether or not to include this on a distro > level since if you have it enabled in one place you almost certainly want it > enabled everywhere else (and disabled everywhere if it is disabled). So it's not just Phonon depending on Pulseaudio, then I see the comfort of a distro level switch. > > Now, at the start of this saga there was a question as to whether this should > be a DISTRO_FEATURE or PACKAGECONFIG (or both, ugh). Ultimately the result is > the same - distro policy controls whether this feature is on or off. > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre -- Regards Samuel _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
