Hello Denis,
Denis 'GNUtoo' Carikli <gnu...@cyberdimension.org> writes: > > I did something similar but at the end of the day it means that at each > guix system reconfigure, I end up building Wireshark only for that > reason. > > Here's my version. I don't use wrapping but I've no idea if it's a good > idea or not: I don't really understand what you mean by 'I don't use wrapping' I don't see removal of wrapping in your package definition. To be clear, I am not adding any wrapping, it's already in the package, because it uses qt-build-system. > > I've not looked into it yet, but we also have the option of requiring > users to declare a service just to make Wireshark work under guix > system. Of course the goal is to make a service, the question is how to make it. The problem is the package here, that will still look to incorrect folder. The users will always have to use a service to get capabilities/setuid... > > Some other daemons like singularity or other containers engine also > require that, so maybe they found some way to deal with this dilemma > that requires to do modifications that are undesirable with non > guix-system use of the package. Singularity patches the source to point to /run/privileged/bin, but as I've said previously, I don't think that's a good way to go. IMO it's much better to at least go with 1. check /run/privileged/bin, 2. fallback to the gnu store output. Or posibly replacing 1 with checking PATH. Regards, Rutherther
