gmail-notify process spawning isn't good

[Dario Meloni]

having 2 process instead of one is not a good way to accomplish a such simple work.
There should be just one python process named gmail-notify and not 2 (gmail-notify and python ./notify.py).
Just 2 little changes should be taken

/usr/bin/gmail-notify should not be a shell file but a link to /usr/lib/gmail-notify/notify.py

in /usr/lib/gmail-notify/notify.py 2 line must be added at the top:

import sys
sys.path.append('/usr/lib/gmail-notify');

[Dario Meloni (mellon85)]

Ops. I don't even have noticied that the inclusion of the path is already done.
Then just the link is needed and not a shell script

[David Grant (davidgrant)]

Are you sure this is really necessary? I made the gentoo ebuild and used a script like this:

#!/bin/bash
exec /usr/bin/python /usr/lib/python2.4/site-packages/gmail-notify/notifier.py "$1"

and I don't get 2 processes.

[Dario Meloni (mellon85)]

I thought the link was a good solution, if this one is has the same result then it's ok

[Christian Reis (kiko)]

I am removing this debbugs bug watch because it doesn't appear to actually be valid. Is there a specific bug on bugs.debian.org that you want to link to? I couldn't find any bugs related to gmail-notify there.

[Launchpad Janitor (janitor)]

[Expired for gmail-notify (Ubuntu) because there has been no activity for 60 days.]