Closed warp10 closed 8 years ago
goopg can start gpg-agent easily, nonetheless gpg needs to be configured and restarted to use gpg-agent, and that requires a change in gpg.conf. IMO that's out of the goopg scope, and goopg shouldn't mess with user's gpg configuration.
A better solution might be to add a check and warn the user is gpg-agent is down. Thoughts?
GooPG needs to start automatically gpg-agent, so I do not think this will close #19.
Can you please consider to patch goopg properly ?
Thanks