Do you simply have to add sequoia-sq to home.packages
like home.packages = [ ... sequoia-sq ... ]?
Or is it simply a drop-in replacement of programs.gpg.package
like programs.gpg.package = pkgs.sequoia-sq? else, would the package be pkgs.sequoia-sqv / pkgs.sequoia-sqop / pkgs.sequoia-chameleon-gnupg ?
Unfortunately, from what I’m aware of, sequoia hasn’t yet implemented all of the commands required for also replacing gpg-agent and prompting a password etc. using pinentry. So I wouldn’t use it as a drop-in replacement for programs.gpg.package. See:
I haven’t tried it, personally, and there is no simple home-manager module afaik, so you’d have to experiment with setting it up yourself. I doubt it’s fully functional yet.
I had a deeper look on this subject today, and I wanted to point out a small misconception the this discussion, the READMEs of these projects, and sequoia-chameleon-gnupg’s in particular might suggest:
The main annoying issue with gpg is its non-intuitive CLI interface, based only upon -- prefixed flags and no hierarchy. gpg-sq is using Sequoia’s Rust libraries internally, and also interacts with $GNUPGHOME and gpg-agent, but you can’t use sq to interact with $GNUPGHOME and gpg-agent. That’s why upstream issues #414 and #537 are still open.
Also something very annoying is that git’s gpg.format config option has openpgp as a choice but requires the very GnuPG command interface (in which case git requires sequoia-chameleon-gnupg)
