As I am using this package inside of a snap there can be new limitations that can happen.
Snap is a very confined environment and the developer needs to specify in advance (and sometimes get permission) in order to use different systems calls and info.
This leads me to a new bug that I am not sure how much it is common to get and it is permission denied on using the avahi-browse command.
To fix that and still allow a better way of finding all the SRV lists in Linux if it is possible I am suggesting the following.
Short fix for most cases - by default it will not use the Linux-specific implementation, a boolean value can be passed if needed.
We find a way to catch the error and in case of missing permission it calls the non-Linux specific implementation.
I think 2 will be a little difficult since it is hard to debug the program when it runs as a snap so we can just level it open and not touch it at all.
We can add to it p4 after completing 1 for now.
As I am using this package inside of a snap there can be new limitations that can happen. Snap is a very confined environment and the developer needs to specify in advance (and sometimes get permission) in order to use different systems calls and info.
This leads me to a new bug that I am not sure how much it is common to get and it is permission denied on using the
avahi-browse
command.This is my log.
To fix that and still allow a better way of finding all the SRV lists in Linux if it is possible I am suggesting the following.
I think 2 will be a little difficult since it is hard to debug the program when it runs as a snap so we can just level it open and not touch it at all. We can add to it p4 after completing 1 for now.