Open abathur opened 2 years ago
@clkamp queried about gpg-connect-agent and reported documented 4 execable arguments in https://github.com/abathur/resholve/issues/77#issuecomment-1077698500
gpg-connect-agent
We'll need to triage the rest of them as well, since existing lore for gnupg-2.3.3 flags most of bin/:
$ cat /nix/store/9njl0yzcdmm4zninv6zsqsm09gh4ajbs-gnupg-2.3.3-binlore/execers can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/dirmngr can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/dirmngr-client can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg-agent can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg-card can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg-connect-agent can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg-wks-client can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg-wks-server can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpg2 can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgconf can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgparsemail can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgscm can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgsm can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgtar can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgv can:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/watchgnupg cannot:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/gpgsplit cannot:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/kbxutil might:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/addgnupghome might:/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3/bin/applygnupgdefaults
gnupg also might present a good test-case for wrestling with whether binlore should also be processing lib and libexec?
/nix/store/hp1677srnrsrcj93mg8zwbqr5mlrlhc1-gnupg-2.3.3 ├── bin │ ├── addgnupghome │ ├── applygnupgdefaults │ ├── dirmngr │ ├── dirmngr-client │ ├── gpg │ ├── gpg-agent │ ├── gpg-card │ ├── gpg-connect-agent │ ├── gpg-wks-client │ ├── gpg-wks-server │ ├── gpg2 -> gpg │ ├── gpgconf │ ├── gpgparsemail │ ├── gpgscm │ ├── gpgsm │ ├── gpgsplit │ ├── gpgtar │ ├── gpgv │ ├── kbxutil │ ├── libexec -> ../libexec │ └── watchgnupg ├── lib │ └── systemd │ └── user │ ├── dirmngr.service │ ├── dirmngr.socket │ ├── gpg-agent-browser.socket │ ├── gpg-agent-extra.socket │ ├── gpg-agent-ssh.socket │ ├── gpg-agent.service │ └── gpg-agent.socket ├── libexec │ ├── dirmngr_ldap │ ├── gpg-check-pattern │ ├── gpg-pair-tool │ ├── gpg-preset-passphrase │ ├── gpg-protect-tool │ ├── gpg-wks-client │ ├── keyboxd │ └── scdaemon
@clkamp queried about
gpg-connect-agent
and reported documented 4 execable arguments in https://github.com/abathur/resholve/issues/77#issuecomment-1077698500We'll need to triage the rest of them as well, since existing lore for gnupg-2.3.3 flags most of bin/:
gnupg also might present a good test-case for wrestling with whether binlore should also be processing lib and libexec?