Lennart: First, I should say that I really appreciate your comments, and helping me to understand a whole range of issues, that go far beyond just libcanberra.
>>> The tool might be useful for similar purposes as "zenity": for >>> scripting purposes. >> When run from zenity, it is being run from a program rather than a >> user. Normally libexec is used for things that are typically run from >> programs. > > 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. Thanks for the example. This seems reasonable to me. Based on your examples, I think I can share this information with ARC and get them to be agreeable to install this program in /usr/bin. > 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! Whether something belongs in libexec is always a little fuzzy. I think it is good to discuss to make sure things are put in the right place. Perhaps I've belabored the issue. If so, I apologize. But based on your comments, I agree that it belongs in /bin. > Is it so difficult to understand that I consider having c-g-p > in $PATH to be somewhat part of libcanberra's API? You are welcome to > deviate from that, it's Free Software after all, but please, don't ask > me to do this for you upstream. On the libcanberra sixfold-announcement web page there is a link to the "complete!" documentation, but there doesn't seem to be any docs regarding the fact that c-g-p is considered a part of the API. Also, I couldn't find any docs about the API for writing a backend plugin, which made it a little hard for me to figure out how to write one, and might explain why my GStreamer plugin was a bit hacked. http://0pointer.de/public/libcanberra-html/libcanberra-canberra.html Are the docs for writing a backend plugin API somewhere else? Or do you just have to figure it out from the existing plugin code? >> If someone provides a working patch to specify where it is installed, >> why wouldn't it make sense to just accept it upstream? It seems >> sensible to allow people to configure the module as they want, rather >> than making people configure it when packaging. > > For the same reason that I wouldn't take a patch that, let's say, > extended libcanberra's API to support playing Jingle Bells on your > USB marimba for each event sound. I wouldn't want to see this exposed > in the API, because I don't want to support this in the API. To me, being able to specify install file locations isn't quite as arbitrary as playing Jingle Bells. But, you are the maintainer and you get to make choices like this. That's fine. I was just expressing surprise. I wrote the pkg-config code that allowed ESD to be installed in libexec, and it never seemed to be the sort of maintenance nightmare you seem concerned about. But, whatever. >>> Somehow I managed to ignore that second iteration of the patches and >>> didn't review them when Marc-Andre posted them. However, a few minutes >>> ago I finally reviewed them with Marc-Andre on IRC. He plans to rebase >>> them on current libcanberra. >> Great, does this mean that GStreamer will just be supported >> out-of-the-box with the next libcanberra release? That's great. Or >> do you need further help to make the code ready? > > Note sure about the *next* libcanberra release. That depends entirely > on whether I get a good, mergable patch by then. Consider working with > Marc-Andre to get it ready quickly. Okay. That sounds reasonable. I do not remember you sharing Marc-Andre's contact information. If you could share that with me, I will get in touch with him. Thanks again, Brian _______________________________________________ libcanberra-discuss mailing list [email protected] https://tango.0pointer.de/mailman/listinfo/libcanberra-discuss
