Ubuntu/Debian has never used openresolv, and yes systemd-resolved had a contribution to have openresolv compatible input interface.
I am not asking for wireguard to implement any legacy/compat interfaces, but use directly systemd-resolved standard interface which has abi guarantees.
There is a lot more things and options one can provide to systemd-resolved via native API that is impossible to specify via openresolv or compat-openresolv.
I do not wish to ship any openresolv/resolvconf/compat symlinks at all going forward.
Integration with resolvconf _without_ using .$suffix of where the DNS information is originating is incorrect integration on Debian/Ubuntu, because of how resolvconf is shipped and configured on Debian/Ubuntu and used by other packages.
Ubuntu/Debian has never used openresolv, and yes systemd-resolved had a contribution to have openresolv compatible input interface.
I am not asking for wireguard to implement any legacy/compat interfaces, but use directly systemd-resolved standard interface which has abi guarantees.
There is a lot more things and options one can provide to systemd-resolved via native API that is impossible to specify via openresolv or compat-openresolv.
I do not wish to ship any openresolv/ resolvconf/ compat symlinks at all going forward.
Integration with resolvconf _without_ using .$suffix of where the DNS information is originating is incorrect integration on Debian/Ubuntu, because of how resolvconf is shipped and configured on Debian/Ubuntu and used by other packages.