Comment 6 for bug 328607

Hi Mirco,
no there is no TCL bindings for libnotify, thanks for adding that text about notify-send in that guideline. As I said before, that's exactly what the notify plugin for aMSN does!
From your mail, it seems that you contacted the author and that you require some changes to the notify plugin for it to work on jaunty.. however I don't understand, if we use notify-send, then it should just work, right ?
Anyways, I spoke to the author in IRC, and he said that apparently (from what he understood) that the jaunty notify-send doesn't support the --timeout option.. I'd like to know more about this.. why did you drop the --timeout option? and what is the timeout if notify-send doesn't support it ? is it a global preference now or something?
Anyways, in my opinion notify-send should not fail if the --timeout option is passed, it should just ignore it if the notify-osd daemon doesn't support the timeout capability (or whatever method you use for determining that stuff), it should just ignore it and maybe output a warning. Removing the option is just a break in the API and unless you rename the tool to notify-send2 or something, then it's really bad for backward compatibility, etc...
Anyways, what solution do you propose? How can we see if the notify-send on the system is the one from jaunty or from an older version or other distro? Do we need a hack in the code to do a 'exec notify-send --help | grep timeout' to see if it supports the option ?
I personally think that all of this is not an aMSN bug, I think it should be reassigned as a notify-send bug because it breaks compatibility...

Anyways, if I misunderstood, then sorry about the rant.. then could you please explain to us in detail what exactly is it that you need modified in the notify plugin for it to be the way you like? And if some jaunty specific changes are necessary, can you describe exactly how we can do a check to see what notify-send supports or doesn't support?
And if I was right, tell me what you think about reassigning the bug as a notify-send bug since it breaks backward compatibility.

p.s: I gave the link to this bug to the plugin's author, so I think it would be best to keep all further discussion here for completeness and to keep everything public, instead of having half the info in a private mail to someone.

Thanks,
KaKaRoTo