Control: tag -1 + upstream Hi Ximin!
> Hi, gpg2 is getting more usage. Please allow parcimonie to work with > it, e.g. by a CLI or ENV setting. Yes! I've got bad news: I probably won't have time to do that myself soon. I've got good news: * I'm using parcimonie vith gpg2 myself (I've got a gpg symlink somewhere in my $PATH before /usr/bin, that points to /usr/bin/gpg2). Works for me. * The library used by parcimonie to talk to gpg (GnuPG::Interface) theoretically supports using an arbitrary gpg binary name (via the `call' attribute in the GnuPG::Interface class). => that's just a matter of crazy OO plumbing. Supporting a arbitrary gpg executable path may be non-trivial (I bet the value of `call' must be a single word, and then one needs to generate the wrapper dynamically, which feels ugly; it also could make it harder to add an AppArmor profile later). Supporting gpg2 (wherever it is in $PATH) looks trivial. For anyone interested (and possibly myself some day): * add a parcimonie-torified-gpg2 wrapper * add a gpg2 option attribute to App::Parcimonie::Daemon, with type Bool (see e.g. "option 'gnupg_already_torified'") * for every function in App::Parcimonie, where an App::Parcimonie::GnuPG::Interface is instantiated (e.g. gpgPublicKeys), their caller (in generally in ::Daemon) should pass them something like that in the additional options hash (%gi_args) they take: call => 'gpg2' * add a gpg2 attribute to App::Parcimonie::GnuPG::Interface, adjust its "after 'BUILD'" to call parcimonie-torified-gpg2 as needed * submit a Git pull request against git://gaffer.ptitcanardnoir.org/App-Parcimonie.git > One workaround in the meantime is to edit > /usr/bin/parcimonie-torsocks-gpg, but of course this changes things > for the entire system. > I also tried putting an override in ~/bin/ and adding this to PATH, > but it didn't work. I find this surprising, given I use a very similar solution. Are you sure parcimonie knew about ~/bin/ being in the $PATH, in the environment where it was launched? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
