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
