Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for gpg2 #26

Open
DamienCassou opened this issue Jul 9, 2017 · 4 comments
Open

Support for gpg2 #26

DamienCassou opened this issue Jul 9, 2017 · 4 comments

Comments

@DamienCassou
Copy link

The command gpg is always used to start GnuPG. Would it be possible to add support for gpg2?

@freewil
Copy link
Collaborator

freewil commented Jul 9, 2017

Should be as easy as making this string/path configurable.

We could add a path() func to the module GPG and have that configure the sub-module spawnGPG. That would be a global change, affecting all other code in the same process using this module, but I think that's probably ok. I can't think of too many use cases where you'd use 2 different binaries of gpg in the same process.

@DamienCassou
Copy link
Author

DamienCassou commented Jul 10, 2017 via email

@freewil
Copy link
Collaborator

freewil commented Jul 10, 2017

I took a look at that, it's not a bad approach, but it still requires the user of that module to call find_and_set_cmd() - I'd rather just keep it simple and have the user call path() and set it explicitly

@wswoodruff
Copy link

wswoodruff commented Jul 10, 2017

Yo @DamienCassou This project is a node wrapper around gpg2: https://github.com/wswoodruff/doggo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants