On Mon, Feb 7, 2011 at 3:23 PM, Gilles Dartiguelongue <eva@gentoo.org> wrote:
> Le lundi 07 février 2011 à 08:36 +0100, Ulrich Mueller a écrit :
>> It's used by several packages as a local flag, and its meaning seems
>> to be similar enough.
>>
[snip]
>> gnome-extra/gnome-games:sound - Enable sound using media-libs/libcanberra
[snip]
>
> any gnome packages listed here is a bug if the only pulled dependency is
> libcanberra. The herd has a policy to always depend on libcanberra. It
> is a lightweight library that can be build with no sound output for
> those who don't like it and it saves needless USE flags.
>
Just another datapoint: the GNOME 3 version of gnome-games won't have
USE=sound anymore, I've made it a hard-dependency since almost all the
games use it now.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
02-23-2011, 03:28 PM
Gilles Dartiguelongue
Make "sound" a global USE flag?
Le mercredi 23 février 2011 à 21:04 +0530, Nirbheek Chauhan a écrit :
>
>
> Just another datapoint: the GNOME 3 version of gnome-games won't have
> USE=sound anymore, I've made it a hard-dependency since almost all the
> games use it now.
It's ok, I already dropped it in gentoo-x86 ebuilds
--
Gilles Dartiguelongue <eva@gentoo.org>
Gentoo
02-25-2011, 06:56 AM
Arun Raghavan
Make "sound" a global USE flag?
On 8 February 2011 01:18, Petteri Räty <betelgeuse@gentoo.org> wrote:
> On 02/07/2011 08:08 PM, Samuli Suominen wrote:
[...]
>> The "means" are commonly used as USE flag names with "result" in USE
>> flag description. *Think of "gstreamer", or "xine" for example.
Both of these are reasonably well-known, libcanberra is not. Moreover,
when these are available, they might represent a choice of backends,
with maintainers ideally picking one that is preferable, leaving the
picking an alternative choice to users.
>> But I'm open to suggestions...
>>
>
> How about event-sounds?
>
> "libcanberra is an implementation of the XDG Sound Theme and Name
> Specifications, for generating event sounds on free desktops, such as
> GNOME."
>
> http://0pointer.de/lennart/projects/libcanberra/#overview
This sounds reasonable. Did I miss some conversation somewhere,
because it appears that "libcanberra" got finalised [1] on (even
though I believe it's a horribly unintuitive name to foist on users).
>>>>> On Wed, 23 Feb 2011, Ulrich Mueller wrote:
>>>>> On Tue, 22 Feb 2011, Rich Freeman wrote:
>> Do we really need two different use flags for code-based sound
>> support vs file-based sound inclusion?
> Maybe it's similar enough. So, unify both "audio" and "sounds" with
> the global "sound" flag?