I don't think it's that simple. The addition of seahorse was done in an incomplete way to not work with the pre-existing tools.
You can't add seahorse, have it not work and arbitrarily declare what existed before.
Seahorse also does "fun" things like remove a user's pre-existing gnupg.conf file and replace it with ones that are blank except for a comment that the file was created by seahorse. This breaks anything (like using gnupg-agent) that depends on the config file.
If seahorse would actually provide a compatible, functional agent that could be an alternative, we could handle this quite easily for alternate recommends/depends as we do with the various pinentry variants.
I don't think it's that simple. The addition of seahorse was done in an incomplete way to not work with the pre-existing tools.
You can't add seahorse, have it not work and arbitrarily declare what existed before.
Seahorse also does "fun" things like remove a user's pre-existing gnupg.conf file and replace it with ones that are blank except for a comment that the file was created by seahorse. This breaks anything (like using gnupg-agent) that depends on the config file.
If seahorse would actually provide a compatible, functional agent that could be an alternative, we could handle this quite easily for alternate recommends/depends as we do with the various pinentry variants.