Perhaps we need to think less in terms of packages, and more in terms of integration. Then the packaging needs will become apparent.

• What packages will have resolv needs, now and in the near future, so wireguard etc should be considered part of the solution.
• What tools do they expect to be available?
• Can we integrate it all with one method that will work with all the tools and networkmanager/systemd?
• Does any documentation make sense around this solution?

Sure ! But about the integration I don't know what is possible. Only this I know are:

• It is dedicated to openvpn only
• The user have to edit the /etc/nsswitch.conf and edit his openvpn conf file to add:

script-security 2
setenv PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
up /etc/openvpn/scripts/update-systemd-resolved
down /etc/openvpn/scripts/update-systemd-resolved
down-pre

and, of course, have the system-resolved systemd service started.

So, some guidelines in Solus documentation may be necessary I think if it is packaged.

On openresolv's task, @eric-salo said that update-systemd-resolved fixed dns leaks, maybe he can give you more details.

Some interesting links:

• https://bbs.archlinux.org/viewtopic.php?id=226509
• https://serverfault.com/questions/732317/openvpn-and-systemd-resolved
• https://aaronhorler.com/articles/openvpn-17.10-dns-leak.html
• https://unix.stackexchange.com/questions/434916/how-to-fix-openvpn-dns-leak