From Mon Aug 25 09:56:05 2008 Date: Mon, 25 Aug 2008 09:56:05 -0700 (PDT) From: Postmaster Subject: Message from mail server Content-Length: 95 Mime-Version: 1.0 Status: RO X-IMAP: 1219683365 7 Delete. This is a system message. --END+PSEUDO-- From sacadmin Tue Aug 19 15:37:48 2008 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7JMbmZc002576; Tue, 19 Aug 2008 15:37:48 -0700 (PDT) Received: (from bc99092@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m7JMbmj0002572; Tue, 19 Aug 2008 15:37:48 -0700 (PDT) Date: Tue, 19 Aug 2008 15:37:48 -0700 (PDT) From: Brian Cameron Message-Id: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> To: LSARC@sac.sfbay.sun.com Cc: jds-dev@sun.com Subject: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] Content-Length: 7223 Status: RO X-Status: $$$$ X-UID: 0000000001 Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: libcanberra 1.2. Name of Document Author/Supplier: Author: Jerry Tan 1.3 Date of This Document: 19 August, 2008 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: libcanberra 1.2. Name of Document Author/Supplier: Author: Jerry Tan Sponsor: 1.3. Date of This Document: 18/08/2008 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Robert O'Dea 1.4.4. The name of your business unit: Software - OPG 1.5. Email Aliases: 1.5.1. Responsible Manager: leo.binchy@sun.com 1.5.2. Responsible Engineer: jerry.tan@sun.com 1.5.3. Interest List: jds-dev@sun.com 2. Project Summary 2.1. Project Description: libcanberra is a desktop event sound library. 3. Business Summary Sound effects are an important part of the usability of modern desktops. In the past, GNOME events have been managed by ESD, and managed by libgnome. The GNOME community has long been interested in deprecating the usage of both ESD and libgnome, so this library is intended to be the replacement. The previous solution had a number of problems: a minimal set of defined sound events, no support for theming, and poor integration into applications. libcanberra has been introduced to resolve these problems. 4. Technical Description: 4.1. Details: Similar to the XDG Icon Naming Specification and the XDG Icon Theme Specification, the FreeDesktop.org community has been working to unify event sounds on desktop, so they have created the XDG Sound Theme Specification and the XDG Sound Name Specification. The intent is that these two new specifications will be established as the future standard for sound event theming for free desktops. The libcanberra library is a very small and lean implementation of these specifications. It is also very powerful and provides a more rich set of interfaces. An event sound is triggered via libcanberra by calling the ca_context_play() function on a previously created ca_context object. The ca_context_play() takes a list of key-value pairs that describe the event sound to generate as closely as possible. The most important property is CA_PROP_EVENT_ID which defines the XDG sound name for the sound to play. Here is a code sample: ca_context *c = NULL; /* Create a context for the event sounds for your application */ ca_context_create(&c); /* Set a few application-global properties */ ca_context_change_props(c, CA_PROP_APPLICATION_NAME, "An example", CA_PROP_APPLICATION_ID, "org.freedesktop.libcanberra.Test", CA_PROP_APPLICATION_ICON_NAME, "libcanberra-test", NULL); /* ... */ /* Trigger an event sound */ ca_context_play(c, 0, CA_PROP_EVENT_ID, "button-pressed", /* The XDG sound name */ CA_PROP_MEDIA_NAME, "The user pressed the button foobar", CA_PROP_EVENT_MOUSE_X, "555", CA_PROP_EVENT_MOUSE_Y, "666", CA_PROP_WINDOW_NAME, "Foobar Dialog", CA_PROP_WINDOW_ICON_NAME, "libcanberra-test-foobar-dialog", CA_PROP_WINDOW_X11_DISPLAY, ":0", CA_PROP_WINDOW_X11_XID, "4711", NULL); /* ... */ ca_context_destroy(&c); To simplify libcanberra usage from a GTK+ program, GTK+ bindings are provided by the libcanberra-gtk library. The libcanberra GTK+ module library is used so that sounds associated with GTK+ widget events are played. In other words, by making sure that all GTK+ based programs load this module, they will automatically support sound event theming according to the FreeDesktop specifications. libcanberra supports ogg-vorbis for default system sounds since ogg-vorbis is a good free, compressed standard for desktop audio. 4.2. Interfaces: Exported Interfaces Interface Classification Comments --------------- -------------- --------------------- SUNWlibcanberra Uncommitted the package SUNWlibcanberra-devel Uncommitted the dev package /usr/bin/canberra-gtk-play Volatile tool to play event sounds /usr/lib/libcanberra-gtk.so.0.0.0 Volatile libcanberra library /usr/lib/libcanberra.so.0.0.0 Volatile libcanberra-gtk library /usr/lib/gtk-2.0/modules/ Volatile libcanberra GTK+ libcanberra-gtk-module.so module /usr/lib/libcanberra/ Volatile Plugin directory /usr/lib/libcanberra/sunaudio.so Volatile SunAudio back-end plugin. /usr/lib/pkgconfig/libcanberra-gtk.pc Volatile libcanberra /usr/lib/pkgconfig/libcanberra.pc Volatile pkg-config files /usr/include/canberra-gtk.h Volatile libcanberra-gtk header file /usr/include/canberra.h Volatile libcanberra header file /usr/share/gnome/autostart Volatile login sound /libcanberra-login-sound.desktop /usr/share/gnome/shutdown Volatile logout sound /libcanberra-logout-sound.sh Imported Interfaces Interface Classification Comments --------- -------------- -------- OGG/Vorbis Volatile LSARC/2008/510 GTK+ Uncommitted LSARC/2008/510 SATA (Sun Audio) Committed PSARC/2001/226 4.3. Doc Impact: Man page is needed. 4.4. Packaging & Delivery: SUNWlibcanberra - the package for libcanberra SUNWlibcanberra-devel - the dev package for libcanberra 4.5. Dependencies: 4.6. L10N Impact: The Desktop team is working with the G11N to evaluate and provide I18N/L10N support 4.7 Security Impact: None. 5. Reference Documents: http://0pointer.de/blog/projects/sixfold-announcement.html http://0pointer.de/public/sound-theme-spec.html http://0pointer.de/public/sound-naming-spec.html 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: GNOME 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Brian.Cameron@sun.com Tue Aug 19 15:44:48 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7JMimWp002917 for ; Tue, 19 Aug 2008 15:44:48 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m7JMilB4005788 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 19 Aug 2008 15:44:47 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5V00L1JDUMCU00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 19 Aug 2008 16:44:46 -0600 (MDT) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5V00J9WDULSY10@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 19 Aug 2008 16:44:45 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7JMijfJ008070 for ; Tue, 19 Aug 2008 22:44:45 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5V00M01DPMP600@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 19 Aug 2008 16:44:45 -0600 (MDT) Received: from [10.0.0.41] ([74.41.197.134]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5V00667DUDBBD0@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 19 Aug 2008 16:44:38 -0600 (MDT) Date: Tue, 19 Aug 2008 17:44:46 -0500 From: Brian Cameron Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] Sender: Brian.Cameron@sun.com To: lsarc-ext@sun.com Message-id: <48AB4CDE.1030209@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.16 (X11/20080731) Content-Length: 8341 Status: RO X-Status: $$$$ X-UID: 0000000002 All, I am sponsoring this case for the JDS team in Ireland. The project directory contains the attached proposal. I have set the timer for Monday, August 27th, 2008. This project proposes to integrate libcanberra into a Minor release of Solaris (i.e., Nevada/Open Solaris). This library manages the playback of audio events. These are the audio sounds that are played when you do things like click on a widget. The GNOME community recently decided that this new libcanberra audio event library is now a hard dependency of gnome-control-center. The GNOME desktop will not continue to work with the old libgnome and ESD interfaces for playing desktop audio events. We plan to integrate libcanberra along with GNOME 2.24 so that users have no interruptions with their audio event experience. Thanks, Brian -------- Original Message -------- Subject: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] Date: Tue, 19 Aug 2008 15:37:48 -0700 (PDT) From: Brian Cameron To: LSARC@sac.sfbay.sun.com CC: jds-dev@sun.com Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: libcanberra 1.2. Name of Document Author/Supplier: Author: Jerry Tan 1.3 Date of This Document: 19 August, 2008 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: libcanberra 1.2. Name of Document Author/Supplier: Author: Jerry Tan Sponsor: 1.3. Date of This Document: 18/08/2008 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Robert O'Dea 1.4.4. The name of your business unit: Software - OPG 1.5. Email Aliases: 1.5.1. Responsible Manager: leo.binchy@sun.com 1.5.2. Responsible Engineer: jerry.tan@sun.com 1.5.3. Interest List: jds-dev@sun.com 2. Project Summary 2.1. Project Description: libcanberra is a desktop event sound library. 3. Business Summary Sound effects are an important part of the usability of modern desktops. In the past, GNOME events have been managed by ESD, and managed by libgnome. The GNOME community has long been interested in deprecating the usage of both ESD and libgnome, so this library is intended to be the replacement. The previous solution had a number of problems: a minimal set of defined sound events, no support for theming, and poor integration into applications. libcanberra has been introduced to resolve these problems. 4. Technical Description: 4.1. Details: Similar to the XDG Icon Naming Specification and the XDG Icon Theme Specification, the FreeDesktop.org community has been working to unify event sounds on desktop, so they have created the XDG Sound Theme Specification and the XDG Sound Name Specification. The intent is that these two new specifications will be established as the future standard for sound event theming for free desktops. The libcanberra library is a very small and lean implementation of these specifications. It is also very powerful and provides a more rich set of interfaces. An event sound is triggered via libcanberra by calling the ca_context_play() function on a previously created ca_context object. The ca_context_play() takes a list of key-value pairs that describe the event sound to generate as closely as possible. The most important property is CA_PROP_EVENT_ID which defines the XDG sound name for the sound to play. Here is a code sample: ca_context *c = NULL; /* Create a context for the event sounds for your application */ ca_context_create(&c); /* Set a few application-global properties */ ca_context_change_props(c, CA_PROP_APPLICATION_NAME, "An example", CA_PROP_APPLICATION_ID, "org.freedesktop.libcanberra.Test", CA_PROP_APPLICATION_ICON_NAME, "libcanberra-test", NULL); /* ... */ /* Trigger an event sound */ ca_context_play(c, 0, CA_PROP_EVENT_ID, "button-pressed", /* The XDG sound name */ CA_PROP_MEDIA_NAME, "The user pressed the button foobar", CA_PROP_EVENT_MOUSE_X, "555", CA_PROP_EVENT_MOUSE_Y, "666", CA_PROP_WINDOW_NAME, "Foobar Dialog", CA_PROP_WINDOW_ICON_NAME, "libcanberra-test-foobar-dialog", CA_PROP_WINDOW_X11_DISPLAY, ":0", CA_PROP_WINDOW_X11_XID, "4711", NULL); /* ... */ ca_context_destroy(&c); To simplify libcanberra usage from a GTK+ program, GTK+ bindings are provided by the libcanberra-gtk library. The libcanberra GTK+ module library is used so that sounds associated with GTK+ widget events are played. In other words, by making sure that all GTK+ based programs load this module, they will automatically support sound event theming according to the FreeDesktop specifications. libcanberra supports ogg-vorbis for default system sounds since ogg-vorbis is a good free, compressed standard for desktop audio. 4.2. Interfaces: Exported Interfaces Interface Classification Comments --------------- -------------- --------------------- SUNWlibcanberra Uncommitted the package SUNWlibcanberra-devel Uncommitted the dev package /usr/bin/canberra-gtk-play Volatile tool to play event sounds /usr/lib/libcanberra-gtk.so.0.0.0 Volatile libcanberra library /usr/lib/libcanberra.so.0.0.0 Volatile libcanberra-gtk library /usr/lib/gtk-2.0/modules/ Volatile libcanberra GTK+ libcanberra-gtk-module.so module /usr/lib/libcanberra/ Volatile Plugin directory /usr/lib/libcanberra/sunaudio.so Volatile SunAudio back-end plugin. /usr/lib/pkgconfig/libcanberra-gtk.pc Volatile libcanberra /usr/lib/pkgconfig/libcanberra.pc Volatile pkg-config files /usr/include/canberra-gtk.h Volatile libcanberra-gtk header file /usr/include/canberra.h Volatile libcanberra header file /usr/share/gnome/autostart Volatile login sound /libcanberra-login-sound.desktop /usr/share/gnome/shutdown Volatile logout sound /libcanberra-logout-sound.sh Imported Interfaces Interface Classification Comments --------- -------------- -------- OGG/Vorbis Volatile LSARC/2008/510 GTK+ Uncommitted LSARC/2008/510 SATA (Sun Audio) Committed PSARC/2001/226 4.3. Doc Impact: Man page is needed. 4.4. Packaging & Delivery: SUNWlibcanberra - the package for libcanberra SUNWlibcanberra-devel - the dev package for libcanberra 4.5. Dependencies: 4.6. L10N Impact: The Desktop team is working with the G11N to evaluate and provide I18N/L10N support 4.7 Security Impact: None. 5. Reference Documents: http://0pointer.de/blog/projects/sixfold-announcement.html http://0pointer.de/public/sound-theme-spec.html http://0pointer.de/public/sound-naming-spec.html 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: GNOME 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From John.Fischer@Sun.COM Wed Aug 20 13:32:05 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7KKW5m7003696; Wed, 20 Aug 2008 13:32:05 -0700 (PDT) Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7KKW4mi039839; Wed, 20 Aug 2008 13:32:04 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7KKW4e7017067; Wed, 20 Aug 2008 20:32:04 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5X00H011GREQ00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM); Wed, 20 Aug 2008 14:32:04 -0600 (MDT) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5X0063S2D8JA90@mail-amer.sun.com>; Wed, 20 Aug 2008 14:31:57 -0600 (MDT) Date: Wed, 20 Aug 2008 13:31:56 -0700 From: John Fischer Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] In-reply-to: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> Sender: John.Fischer@Sun.COM To: Brian Cameron Cc: LSARC-ext@sac.sfbay.sun.com, jds-dev@Sun.COM Reply-to: John.Fischer@Sun.COM Message-id: <1219264315.9503.86.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT References: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> Content-Length: 8336 Status: RO X-Status: $$$$ X-UID: 0000000003 Brian, Will the end user use canberra-gtk-play? Or is this only something that the library is intended to use? Are new applications expected to link to libraries within /usr/lib/libcanberra? If not then why isn't this directory and its contents Project Private? Why does it appear that the login and logout mechanisms are different from each other? The login is a desktop file and the logout is a shell script. Is this just a quarky Gnome thing? GTK+ is Uncommitted? I thought that it was Committed. In fact LSARC/2008/510 states that the GTK library is Committed. Thanks, John P.S. I have Cc-ed LSARC-ext instead of just LSARC as this case is open. On Tue, 2008-08-19 at 15:37, Brian Cameron wrote: > Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > libcanberra > 1.2. Name of Document Author/Supplier: > Author: Jerry Tan > 1.3 Date of This Document: > 19 August, 2008 > 4. Technical Description > 1. Introduction > 1.1. Project/Component Working Name: > > libcanberra > > 1.2. Name of Document Author/Supplier: > Author: Jerry Tan > Sponsor: > > 1.3. Date of This Document: > > 18/08/2008 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > > 1.4.1. The PAC or CPT you expect to review your project: > > Solaris PAC > > 1.4.2. The ARC(s) you expect to review your project: > > LSARC > > 1.4.3. The Director/VP who is "Sponsoring" this project: > > Robert O'Dea > > 1.4.4. The name of your business unit: > > Software - OPG > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: leo.binchy@sun.com > 1.5.2. Responsible Engineer: jerry.tan@sun.com > 1.5.3. Interest List: jds-dev@sun.com > > 2. Project Summary > 2.1. Project Description: > > libcanberra is a desktop event sound library. > > 3. Business Summary > > Sound effects are an important part of the usability of modern desktops. > In the past, GNOME events have been managed by ESD, and managed by libgnome. > The GNOME community has long been interested in deprecating the usage > of both ESD and libgnome, so this library is intended to be the replacement. > > The previous solution had a number of problems: a minimal set of defined > sound events, no support for theming, and poor integration into applications. > libcanberra has been introduced to resolve these problems. > > 4. Technical Description: > > 4.1. Details: > > Similar to the XDG Icon Naming Specification and the XDG Icon Theme > Specification, the FreeDesktop.org community has been working to unify > event sounds on desktop, so they have created the XDG Sound Theme > Specification and the XDG Sound Name Specification. The intent is that > these two new specifications will be established as the future standard for > sound event theming for free desktops. > > The libcanberra library is a very small and lean implementation of these > specifications. It is also very powerful and provides a more rich set of > interfaces. > > An event sound is triggered via libcanberra by calling the ca_context_play() > function on a previously created ca_context object. The ca_context_play() > takes a list of key-value pairs that describe the event sound to generate as > closely as possible. The most important property is CA_PROP_EVENT_ID which > defines the XDG sound name for the sound to play. > > Here is a code sample: > > ca_context *c = NULL; > /* Create a context for the event sounds for your application */ > ca_context_create(&c); > /* Set a few application-global properties */ > ca_context_change_props(c, > CA_PROP_APPLICATION_NAME, "An example", > CA_PROP_APPLICATION_ID, "org.freedesktop.libcanberra.Test", > CA_PROP_APPLICATION_ICON_NAME, "libcanberra-test", > NULL); > > /* ... */ > > /* Trigger an event sound */ > ca_context_play(c, 0, > CA_PROP_EVENT_ID, "button-pressed", /* The XDG sound name */ > CA_PROP_MEDIA_NAME, "The user pressed the button foobar", > CA_PROP_EVENT_MOUSE_X, "555", > CA_PROP_EVENT_MOUSE_Y, "666", > CA_PROP_WINDOW_NAME, "Foobar Dialog", > CA_PROP_WINDOW_ICON_NAME, "libcanberra-test-foobar-dialog", > CA_PROP_WINDOW_X11_DISPLAY, ":0", > CA_PROP_WINDOW_X11_XID, "4711", > NULL); > > /* ... */ > > ca_context_destroy(&c); > > To simplify libcanberra usage from a GTK+ program, GTK+ bindings are > provided by the libcanberra-gtk library. > > The libcanberra GTK+ module library is used so that sounds associated with > GTK+ widget events are played. In other words, by making sure that all GTK+ > based programs load this module, they will automatically support sound event > theming according to the FreeDesktop specifications. > > libcanberra supports ogg-vorbis for default system sounds since ogg-vorbis > is a good free, compressed standard for desktop audio. > > 4.2. Interfaces: > > Exported Interfaces > > Interface Classification Comments > --------------- -------------- --------------------- > SUNWlibcanberra Uncommitted the package > SUNWlibcanberra-devel Uncommitted the dev package > > /usr/bin/canberra-gtk-play Volatile tool to play event > sounds > /usr/lib/libcanberra-gtk.so.0.0.0 Volatile libcanberra library > /usr/lib/libcanberra.so.0.0.0 Volatile libcanberra-gtk > library > /usr/lib/gtk-2.0/modules/ Volatile libcanberra GTK+ > libcanberra-gtk-module.so module > /usr/lib/libcanberra/ Volatile Plugin directory > /usr/lib/libcanberra/sunaudio.so Volatile SunAudio back-end > plugin. > /usr/lib/pkgconfig/libcanberra-gtk.pc Volatile libcanberra > /usr/lib/pkgconfig/libcanberra.pc Volatile pkg-config files > > /usr/include/canberra-gtk.h Volatile libcanberra-gtk > header file > /usr/include/canberra.h Volatile libcanberra header > file > /usr/share/gnome/autostart Volatile login sound > /libcanberra-login-sound.desktop > /usr/share/gnome/shutdown Volatile logout sound > /libcanberra-logout-sound.sh > > Imported Interfaces > > Interface Classification Comments > --------- -------------- -------- > OGG/Vorbis Volatile LSARC/2008/510 > GTK+ Uncommitted LSARC/2008/510 > SATA (Sun Audio) Committed PSARC/2001/226 > > 4.3. Doc Impact: > Man page is needed. > > 4.4. Packaging & Delivery: > > SUNWlibcanberra - the package for libcanberra > SUNWlibcanberra-devel - the dev package for libcanberra > > 4.5. Dependencies: > > > 4.6. L10N Impact: > The Desktop team is working with the G11N to evaluate and provide > I18N/L10N support > > 4.7 Security Impact: > > None. > > 5. Reference Documents: > > http://0pointer.de/blog/projects/sixfold-announcement.html > http://0pointer.de/public/sound-theme-spec.html > http://0pointer.de/public/sound-naming-spec.html > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > GNOME > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > From Brian.Cameron@Sun.COM Thu Aug 21 01:09:25 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7L89Pgw000840; Thu, 21 Aug 2008 01:09:25 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7L89PK8056100; Thu, 21 Aug 2008 01:09:25 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7L89PB7004089; Thu, 21 Aug 2008 08:09:25 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5X00101YJ4PS00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM); Thu, 21 Aug 2008 02:09:25 -0600 (MDT) Received: from [10.0.0.135] ([66.191.58.215]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5X00AKMYNOUPD0@mail-amer.sun.com>; Thu, 21 Aug 2008 02:09:25 -0600 (MDT) Date: Thu, 21 Aug 2008 03:09:33 -0500 From: Brian Cameron Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] In-reply-to: <1219264315.9503.86.camel@sr1-umpk-16> Sender: Brian.Cameron@Sun.COM To: John.Fischer@Sun.COM Cc: Brian Cameron , LSARC-ext@sac.sfbay.sun.com, jds-dev@Sun.COM Message-id: <48AD22BD.1040902@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT References: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> <1219264315.9503.86.camel@sr1-umpk-16> User-Agent: Thunderbird 2.0.0.16 (X11/20080731) Content-Length: 2778 Status: RO X-Status: $$$$ X-UID: 0000000004 John: I would like this ARC case to also cover integrating of the xdg-sound-theme module. I added the following text to the one-pager. Along with libcanberra, this case will also integrate the xdg-sound-theme module. The xdg-sound-theme module only contains audio media files which are installed to the /usr/share/sounds/freedesktop directory. These are the default sound event sounds. As explained above, the xdg-sound-theme module only contains the actual audio files for the default theme used by libcanberra. It doesn't contain any code or anything particularly interesting. Releating to this, I added the following two lines to the Exported Interface table to cover these audio file theme installation interfaces. /usr/share/sounds Uncommitted XDG Sound Theme installation directory. /usr/share/sounds/freedesktop Volatile Default sound theme. > Will the end user use canberra-gtk-play? Or is this > only something that the library is intended to use? The canberra-gtk-play program is intended to be used by programs which want to play sound events. For example, the autostart desktop file /usr/share/gnome/autostart/libcanberra-login-sound.desktop uses canberra-gtk-play to play the login sound. I added the above paragraph to the one pager. > Are new applications expected to link to libraries > within /usr/lib/libcanberra? If not then why isn't > this directory and its contents Project Private? No. These are plugins used by libcanberra itself. It isn't private because an end user might want to write their own plugin if they want libcanberra to support a different audio output mechanism (such as ESD or something). The intention is that end users can write their own plugins as needed. > Why does it appear that the login and logout mechanisms > are different from each other? The login is a desktop > file and the logout is a shell script. Is this just a > quarky Gnome thing? These are the interfaces as defined by gnome-session. Refer to the LSARC 2008/510 GNOME 2.24 ARC materials (the file interface-table.txt) and you'll see that gnome-session installs a "gnome-logout-sound.sh" file to the "shutdown" directory. > GTK+ is Uncommitted? I thought that it was Committed. > In fact LSARC/2008/510 states that the GTK library is > Committed. Thanks for catching this. This is now updated in the case materials. > P.S. I have Cc-ed LSARC-ext instead of just LSARC > as this case is open. Thanks, Brian From John.Fischer@Sun.COM Thu Aug 21 08:25:21 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7LFPLA6011314; Thu, 21 Aug 2008 08:25:21 -0700 (PDT) Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7LFPLbl051187; Thu, 21 Aug 2008 08:25:21 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7LFPKYZ021030; Thu, 21 Aug 2008 15:25:20 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5Y00F01IMRLP00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM); Thu, 21 Aug 2008 09:25:20 -0600 (MDT) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5Y00AOIIU05WF0@mail-amer.sun.com>; Thu, 21 Aug 2008 09:25:14 -0600 (MDT) Date: Thu, 21 Aug 2008 08:25:12 -0700 From: John Fischer Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] In-reply-to: <48AD22BD.1040902@sun.com> Sender: John.Fischer@Sun.COM To: Brian Cameron Cc: John Fischer , Brian Cameron , LSARC-ext@sac.sfbay.sun.com, jds-dev@Sun.COM Reply-to: John.Fischer@Sun.COM Message-id: <1219332310.9503.92.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain Content-transfer-encoding: 7BIT References: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> <1219264315.9503.86.camel@sr1-umpk-16> <48AD22BD.1040902@sun.com> Content-Length: 3267 Status: RO X-Status: $$$$ X-UID: 0000000005 Brian, I am fine with all the answer except the one about canberra-gtk-play. Why should this program be in /usr/bin and not /usr/lib? It seems that it should be declared Project Private and contracts created for applications wanting to us it. Can you explain why that is not the case? Thanks, John On Thu, 2008-08-21 at 01:09, Brian Cameron wrote: > John: > > I would like this ARC case to also cover integrating of the > xdg-sound-theme module. I added the following text to the one-pager. > > Along with libcanberra, this case will also integrate the > xdg-sound-theme module. The xdg-sound-theme module only contains > audio media files which are installed to the > /usr/share/sounds/freedesktop directory. These are the default sound > event sounds. > > As explained above, the xdg-sound-theme module only contains the actual > audio files for the default theme used by libcanberra. It doesn't > contain any code or anything particularly interesting. Releating to > this, I added the following two lines to the Exported Interface table > to cover these audio file theme installation interfaces. > > /usr/share/sounds Uncommitted XDG Sound > Theme > installation > directory. > /usr/share/sounds/freedesktop Volatile Default sound > theme. > > > Will the end user use canberra-gtk-play? Or is this > > only something that the library is intended to use? > > The canberra-gtk-play program is intended to be used by programs > which want to play sound events. For example, the autostart desktop > file /usr/share/gnome/autostart/libcanberra-login-sound.desktop uses > canberra-gtk-play to play the login sound. > > I added the above paragraph to the one pager. > > > Are new applications expected to link to libraries > > within /usr/lib/libcanberra? If not then why isn't > > this directory and its contents Project Private? > > No. These are plugins used by libcanberra itself. It isn't > private because an end user might want to write their own > plugin if they want libcanberra to support a different > audio output mechanism (such as ESD or something). The > intention is that end users can write their own plugins > as needed. > > > Why does it appear that the login and logout mechanisms > > are different from each other? The login is a desktop > > file and the logout is a shell script. Is this just a > > quarky Gnome thing? > > These are the interfaces as defined by gnome-session. Refer > to the LSARC 2008/510 GNOME 2.24 ARC materials (the file > interface-table.txt) and you'll see that gnome-session installs a > "gnome-logout-sound.sh" file to the "shutdown" directory. > > > GTK+ is Uncommitted? I thought that it was Committed. > > In fact LSARC/2008/510 states that the GTK library is > > Committed. > > Thanks for catching this. This is now updated in the case materials. > > > P.S. I have Cc-ed LSARC-ext instead of just LSARC > > as this case is open. > > Thanks, > > Brian From Brian.Cameron@Sun.COM Sun Aug 24 11:32:49 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7OIWnWi000301; Sun, 24 Aug 2008 11:32:49 -0700 (PDT) Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7OIWmqB050149; Sun, 24 Aug 2008 11:32:49 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7OIWmwd020994; Sun, 24 Aug 2008 18:32:48 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K6400E01BIBD700@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM); Sun, 24 Aug 2008 12:32:48 -0600 (MDT) Received: from [192.168.1.108] ([67.167.213.227]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K6400KK4BIN2T60@mail-amer.sun.com>; Sun, 24 Aug 2008 12:32:48 -0600 (MDT) Date: Sun, 24 Aug 2008 13:32:58 -0500 From: Brian Cameron Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] In-reply-to: <1219332310.9503.92.camel@sr1-umpk-16> Sender: Brian.Cameron@Sun.COM To: John.Fischer@Sun.COM Cc: Brian Cameron , LSARC-ext@sac.sfbay.sun.com, jds-dev@Sun.COM Message-id: <48B1A95A.7090807@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> <1219264315.9503.86.camel@sr1-umpk-16> <48AD22BD.1040902@sun.com> <1219332310.9503.92.camel@sr1-umpk-16> User-Agent: Thunderbird 2.0.0.16 (X11/20080731) Content-Length: 4742 Status: RO X-Status: $$$$ X-UID: 0000000006 John: > I am fine with all the answer except the one about canberra-gtk-play. > Why should this program be in /usr/bin and not /usr/lib? It seems > that it should be declared Project Private and contracts created > for applications wanting to us it. Can you explain why that is > not the case? I have discussed this on the libcanberra mailing list over the past few days. Refer to the thread "Getting libcanberra working on Solaris": https://tango.0pointer.de/pipermail/libcanberra-discuss/2008-August/date.html The maintainer suggests that this program is really only used by various programs to play system sounds. Therefore, it sounds like this belongs in libexec. However, the maintainer wants to keep it in /usr/bin to make it easier to script from zenity and to make it easier for developers to use it. I have highlighted that these are not really strong reasons for putting this into /usr/bin. After all, developers should be smart enough to run a program from libexec, and running it from a script is not really an example of an "end user" needing to use it. The libcanberra maintainer seems resistant to moving the program, and also seems resistant to making it possible to configure libcanberra to install to a different location. He says we can obviously change the way we package the module if we want, but it doesn't sound like we will get any upstream support. Unless I can convince the maintainer otherwise, I think it might make the most sense to ship this program in a consistent manner as upstream in /usr/bin. If the committee feels strongly that we need to install this to libexec, then we will need to maintain patches to do so. But it is possible to move it to libexec if we want. Brian > Thanks, > > John > > On Thu, 2008-08-21 at 01:09, Brian Cameron wrote: >> John: >> >> I would like this ARC case to also cover integrating of the >> xdg-sound-theme module. I added the following text to the one-pager. >> >> Along with libcanberra, this case will also integrate the >> xdg-sound-theme module. The xdg-sound-theme module only contains >> audio media files which are installed to the >> /usr/share/sounds/freedesktop directory. These are the default sound >> event sounds. >> >> As explained above, the xdg-sound-theme module only contains the actual >> audio files for the default theme used by libcanberra. It doesn't >> contain any code or anything particularly interesting. Releating to >> this, I added the following two lines to the Exported Interface table >> to cover these audio file theme installation interfaces. >> >> /usr/share/sounds Uncommitted XDG Sound >> Theme >> installation >> directory. >> /usr/share/sounds/freedesktop Volatile Default sound >> theme. >> >>> Will the end user use canberra-gtk-play? Or is this >>> only something that the library is intended to use? >> The canberra-gtk-play program is intended to be used by programs >> which want to play sound events. For example, the autostart desktop >> file /usr/share/gnome/autostart/libcanberra-login-sound.desktop uses >> canberra-gtk-play to play the login sound. >> >> I added the above paragraph to the one pager. >> >>> Are new applications expected to link to libraries >>> within /usr/lib/libcanberra? If not then why isn't >>> this directory and its contents Project Private? >> No. These are plugins used by libcanberra itself. It isn't >> private because an end user might want to write their own >> plugin if they want libcanberra to support a different >> audio output mechanism (such as ESD or something). The >> intention is that end users can write their own plugins >> as needed. >> >>> Why does it appear that the login and logout mechanisms >>> are different from each other? The login is a desktop >>> file and the logout is a shell script. Is this just a >>> quarky Gnome thing? >> These are the interfaces as defined by gnome-session. Refer >> to the LSARC 2008/510 GNOME 2.24 ARC materials (the file >> interface-table.txt) and you'll see that gnome-session installs a >> "gnome-logout-sound.sh" file to the "shutdown" directory. >> >>> GTK+ is Uncommitted? I thought that it was Committed. >>> In fact LSARC/2008/510 states that the GTK library is >>> Committed. >> Thanks for catching this. This is now updated in the case materials. >> >>> P.S. I have Cc-ed LSARC-ext instead of just LSARC >>> as this case is open. >> Thanks, >> >> Brian > From Brian.Cameron@Sun.COM Mon Aug 25 09:39:48 2008 Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7PGdldV012378; Mon, 25 Aug 2008 09:39:47 -0700 (PDT) Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7PGdled006020; Mon, 25 Aug 2008 09:39:47 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7PGdlE0011736; Mon, 25 Aug 2008 16:39:47 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K6600I010MTHA00@mail-amer.sun.com> (original mail from Brian.Cameron@Sun.COM); Mon, 25 Aug 2008 10:39:47 -0600 (MDT) Received: from [129.153.250.143] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K6600A8U0XYQBA0@mail-amer.sun.com>; Mon, 25 Aug 2008 10:39:35 -0600 (MDT) Date: Mon, 25 Aug 2008 11:39:44 -0500 From: Brian Cameron Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] In-reply-to: <48B1A95A.7090807@sun.com> Sender: Brian.Cameron@Sun.COM To: Brian Cameron Cc: John.Fischer@Sun.COM, Brian Cameron , LSARC-ext@sac.sfbay.sun.com, jds-dev@Sun.COM Message-id: <48B2E050.3020708@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> <1219264315.9503.86.camel@sr1-umpk-16> <48AD22BD.1040902@sun.com> <1219332310.9503.92.camel@sr1-umpk-16> <48B1A95A.7090807@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Content-Length: 6235 Status: RO X-Status: $$$$ X-UID: 0000000007 John: In discussing further with the libcanberra maintainer, he had the following to say about canberra-gtk-play: ---- I meant that c-g-p may be used for similar purposes as zenity, not *by* zenity: it may be called from shell scripts and the like. For example, I am using a shell script that plays the "completion" sound via c-g-p after each "make" call. That way I get notified via sound when a long-running PA build finished compiling. If you guys ship zenity in /usr/bin, then you should ship c-g-p in /usr/bin too -- that's all I wanted to say. Think of jhbuild. We could extend it easily to call c-g-p for the completion sound after each build. However, for supporting Solaris we'd have to add some logic to check in which strange path you guys installed it in. I'd consider c-g-p as part of the API of libcanberra: not so much a C API, but an API for shell scripts, and that's why it should be present in $PATH. Or the other way round: following your logic that all binaries that aren't normally started directly by end users should be moved to libexec you should probably start moving the shell itself to libexec! And grep. And cc. And yacc. And so on. All those tools are only used by admins, hackers and shell scripts too! ---- Based on this, I think it is appropriate for it to be installed to bin, rather than libexec. Brian >> I am fine with all the answer except the one about canberra-gtk-play. >> Why should this program be in /usr/bin and not /usr/lib? It seems >> that it should be declared Project Private and contracts created >> for applications wanting to us it. Can you explain why that is >> not the case? > > I have discussed this on the libcanberra mailing list over the past few > days. Refer to the thread "Getting libcanberra working on Solaris": > > https://tango.0pointer.de/pipermail/libcanberra-discuss/2008-August/date.html > > > The maintainer suggests that this program is really only used by > various programs to play system sounds. Therefore, it sounds like > this belongs in libexec. However, the maintainer wants to keep it in > /usr/bin to make it easier to script from zenity and to make it easier > for developers to use it. > > I have highlighted that these are not really strong reasons for > putting this into /usr/bin. After all, developers should be smart > enough to run a program from libexec, and running it from a script > is not really an example of an "end user" needing to use it. > > The libcanberra maintainer seems resistant to moving the program, > and also seems resistant to making it possible to configure libcanberra > to install to a different location. He says we can obviously change > the way we package the module if we want, but it doesn't sound like > we will get any upstream support. > > Unless I can convince the maintainer otherwise, I think it might make > the most sense to ship this program in a consistent manner as upstream > in /usr/bin. If the committee feels strongly that we need to install > this to libexec, then we will need to maintain patches to do so. But > it is possible to move it to libexec if we want. > > Brian > > > >> Thanks, >> >> John >> >> On Thu, 2008-08-21 at 01:09, Brian Cameron wrote: >>> John: >>> >>> I would like this ARC case to also cover integrating of the >>> xdg-sound-theme module. I added the following text to the one-pager. >>> >>> Along with libcanberra, this case will also integrate the >>> xdg-sound-theme module. The xdg-sound-theme module only contains >>> audio media files which are installed to the >>> /usr/share/sounds/freedesktop directory. These are the default >>> sound >>> event sounds. >>> >>> As explained above, the xdg-sound-theme module only contains the actual >>> audio files for the default theme used by libcanberra. It doesn't >>> contain any code or anything particularly interesting. Releating to >>> this, I added the following two lines to the Exported Interface table >>> to cover these audio file theme installation interfaces. >>> >>> /usr/share/sounds Uncommitted XDG Sound >>> Theme >>> installation >>> directory. >>> /usr/share/sounds/freedesktop Volatile Default sound >>> theme. >>> >>>> Will the end user use canberra-gtk-play? Or is this >>>> only something that the library is intended to use? >>> The canberra-gtk-play program is intended to be used by programs >>> which want to play sound events. For example, the autostart desktop >>> file /usr/share/gnome/autostart/libcanberra-login-sound.desktop uses >>> canberra-gtk-play to play the login sound. >>> >>> I added the above paragraph to the one pager. >>> >>>> Are new applications expected to link to libraries >>>> within /usr/lib/libcanberra? If not then why isn't this directory >>>> and its contents Project Private? >>> No. These are plugins used by libcanberra itself. It isn't >>> private because an end user might want to write their own >>> plugin if they want libcanberra to support a different >>> audio output mechanism (such as ESD or something). The >>> intention is that end users can write their own plugins >>> as needed. >>> >>>> Why does it appear that the login and logout mechanisms >>>> are different from each other? The login is a desktop >>>> file and the logout is a shell script. Is this just a >>>> quarky Gnome thing? >>> These are the interfaces as defined by gnome-session. Refer >>> to the LSARC 2008/510 GNOME 2.24 ARC materials (the file >>> interface-table.txt) and you'll see that gnome-session installs a >>> "gnome-logout-sound.sh" file to the "shutdown" directory. >>> >>>> GTK+ is Uncommitted? I thought that it was Committed. >>>> In fact LSARC/2008/510 states that the GTK library is >>>> Committed. >>> Thanks for catching this. This is now updated in the case materials. >>> >>>> P.S. I have Cc-ed LSARC-ext instead of just LSARC >>>> as this case is open. >>> Thanks, >>> >>> Brian >> > From John.Fischer@Sun.COM Tue Sep 9 11:03:57 2008 Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m89I3vNi015662 for ; Tue, 9 Sep 2008 11:03:57 -0700 (PDT) Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m89I3vtu063626 for ; Tue, 9 Sep 2008 11:03:57 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m89I3qAQ022880 for ; Tue, 9 Sep 2008 11:03:52 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K6X00101TT6RH00@fe-sfbay-10.sun.com> (original mail from John.Fischer@Sun.COM) for LSARC-ext@sac.sfbay.sun.com; Tue, 09 Sep 2008 11:03:52 -0700 (PDT) Received: from [192.168.10.13] ([76.20.56.47]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K6X00IYJWUASA10@fe-sfbay-10.sun.com>; Tue, 09 Sep 2008 11:03:47 -0700 (PDT) Date: Tue, 09 Sep 2008 11:03:30 -0700 From: John Fischer Subject: Re: libcanberra [LSARC/2008/534 FastTrack timeout 08/27/2008] In-reply-to: <48B2E050.3020708@sun.com> Sender: John.Fischer@Sun.COM To: Brian Cameron Cc: LSARC-ext@sac.sfbay.sun.com, jds-dev@Sun.COM Reply-to: John.Fischer@Sun.COM Message-id: <48C6BA72.6050508@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <200808192237.m7JMbmj0002572@sac.sfbay.sun.com> <1219264315.9503.86.camel@sr1-umpk-16> <48AD22BD.1040902@sun.com> <1219332310.9503.92.camel@sr1-umpk-16> <48B1A95A.7090807@sun.com> <48B2E050.3020708@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 6564 All, I am fine with this. Since there are no other issues I am closing this case as approved. Thanks, John Brian Cameron wrote: > > John: > > In discussing further with the libcanberra maintainer, he had the > following to say about canberra-gtk-play: > > ---- > > I meant that c-g-p may be used for similar purposes as zenity, not *by* > zenity: it may be called from shell scripts and the like. > > For example, I am using a shell script that plays the "completion" > sound via c-g-p after each "make" call. That way I get notified via > sound when a long-running PA build finished compiling. > > If you guys ship zenity in /usr/bin, then you should ship c-g-p in > /usr/bin too -- that's all I wanted to say. > > Think of jhbuild. We could extend it easily to call c-g-p for the > completion sound after each build. However, for supporting Solaris > we'd have to add some logic to check in which strange path you guys > installed it in. > > I'd consider c-g-p as part of the API of libcanberra: not so much a C > API, but an API for shell scripts, and that's why it should be present > in $PATH. Or the other way round: following your logic that all > binaries that aren't normally started directly by end users should be > moved to libexec you should probably start moving the shell itself to > libexec! And grep. And cc. And yacc. And so on. All those tools are > only used by admins, hackers and shell scripts too! > > ---- > > Based on this, I think it is appropriate for it to be installed to > bin, rather than libexec. > > Brian > > >>> I am fine with all the answer except the one about canberra-gtk-play. >>> Why should this program be in /usr/bin and not /usr/lib? It seems >>> that it should be declared Project Private and contracts created >>> for applications wanting to us it. Can you explain why that is >>> not the case? >> >> I have discussed this on the libcanberra mailing list over the past few >> days. Refer to the thread "Getting libcanberra working on Solaris": >> >> https://tango.0pointer.de/pipermail/libcanberra-discuss/2008-August/date.html >> >> >> The maintainer suggests that this program is really only used by >> various programs to play system sounds. Therefore, it sounds like >> this belongs in libexec. However, the maintainer wants to keep it in >> /usr/bin to make it easier to script from zenity and to make it easier >> for developers to use it. >> >> I have highlighted that these are not really strong reasons for >> putting this into /usr/bin. After all, developers should be smart >> enough to run a program from libexec, and running it from a script >> is not really an example of an "end user" needing to use it. >> >> The libcanberra maintainer seems resistant to moving the program, >> and also seems resistant to making it possible to configure libcanberra >> to install to a different location. He says we can obviously change >> the way we package the module if we want, but it doesn't sound like >> we will get any upstream support. >> >> Unless I can convince the maintainer otherwise, I think it might make >> the most sense to ship this program in a consistent manner as upstream >> in /usr/bin. If the committee feels strongly that we need to install >> this to libexec, then we will need to maintain patches to do so. But >> it is possible to move it to libexec if we want. >> >> Brian >> >> >> >>> Thanks, >>> >>> John >>> >>> On Thu, 2008-08-21 at 01:09, Brian Cameron wrote: >>>> John: >>>> >>>> I would like this ARC case to also cover integrating of the >>>> xdg-sound-theme module. I added the following text to the one-pager. >>>> >>>> Along with libcanberra, this case will also integrate the >>>> xdg-sound-theme module. The xdg-sound-theme module only contains >>>> audio media files which are installed to the >>>> /usr/share/sounds/freedesktop directory. These are the default >>>> sound >>>> event sounds. >>>> >>>> As explained above, the xdg-sound-theme module only contains the actual >>>> audio files for the default theme used by libcanberra. It doesn't >>>> contain any code or anything particularly interesting. Releating to >>>> this, I added the following two lines to the Exported Interface table >>>> to cover these audio file theme installation interfaces. >>>> >>>> /usr/share/sounds Uncommitted XDG Sound >>>> Theme >>>> installation >>>> directory. >>>> /usr/share/sounds/freedesktop Volatile Default >>>> sound >>>> theme. >>>> >>>>> Will the end user use canberra-gtk-play? Or is this >>>>> only something that the library is intended to use? >>>> The canberra-gtk-play program is intended to be used by programs >>>> which want to play sound events. For example, the autostart >>>> desktop >>>> file /usr/share/gnome/autostart/libcanberra-login-sound.desktop >>>> uses >>>> canberra-gtk-play to play the login sound. >>>> >>>> I added the above paragraph to the one pager. >>>> >>>>> Are new applications expected to link to libraries >>>>> within /usr/lib/libcanberra? If not then why isn't this directory >>>>> and its contents Project Private? >>>> No. These are plugins used by libcanberra itself. It isn't >>>> private because an end user might want to write their own >>>> plugin if they want libcanberra to support a different >>>> audio output mechanism (such as ESD or something). The >>>> intention is that end users can write their own plugins >>>> as needed. >>>> >>>>> Why does it appear that the login and logout mechanisms >>>>> are different from each other? The login is a desktop >>>>> file and the logout is a shell script. Is this just a >>>>> quarky Gnome thing? >>>> These are the interfaces as defined by gnome-session. Refer >>>> to the LSARC 2008/510 GNOME 2.24 ARC materials (the file >>>> interface-table.txt) and you'll see that gnome-session installs a >>>> "gnome-logout-sound.sh" file to the "shutdown" directory. >>>> >>>>> GTK+ is Uncommitted? I thought that it was Committed. >>>>> In fact LSARC/2008/510 states that the GTK library is >>>>> Committed. >>>> Thanks for catching this. This is now updated in the case materials. >>>> >>>>> P.S. I have Cc-ed LSARC-ext instead of just LSARC >>>>> as this case is open. >>>> Thanks, >>>> >>>> Brian >>> >> >