"Could snapd be so smart to copy the .service file into /usr/share/dbus/services/ when the interface gets connected, and unlink it when it gets disconnected?"
Yes it could and that sounds like a reasonable approach if it is properly designed, but I think that is a different problem than what PR #1613 is trying to solve. I mention "properly designed" because "when the interface gets connected" would have to be expressed as a plug so that it could be connected/disconnected and as such, likely a different interface, such as 'dbus-activation-support' or something.
"Could snapd be so smart to copy the .service file into /usr/share/ dbus/services/ when the interface gets connected, and unlink it when it gets disconnected?"
Yes it could and that sounds like a reasonable approach if it is properly designed, but I think that is a different problem than what PR #1613 is trying to solve. I mention "properly designed" because "when the interface gets connected" would have to be expressed as a plug so that it could be connected/ disconnected and as such, likely a different interface, such as 'dbus-activatio n-support' or something.