- name: yabridge
- description: Windows audio plugin bridge for Linux (VST2/VST3/CLAP)
- snapcraft: yabridge-snap/snap/snapcraft.yaml at main · eeickmeyer/yabridge-snap · GitHub
- upstream: GitHub - robbert-vdh/yabridge: A modern and transparent way to use Windows VST2, VST3 and CLAP plugins on Linux · GitHub
- upstream-relation: packager, Ubuntu MOTU
- interfaces:
- personal-files:
-
request-type: auto-connection
-
reasoning: yabridge bridges Windows audio plugins (VST2/VST3/CLAP) to Linux DAWs. It requires write access to ~/.local/share/yabridge (where the wrapper symlinks bridge files for runtime discovery), ~/.config/yabridgectl (XDG config path for yabridgectl), and ~/.vst, ~/.vst3, ~/.clap (industry-standard Linux plugin directories defined by the VST2, VST3 SDK, and CLAP specifications, where bridged plugin files are installed for DAW discovery). It requires read access to ~/.wine to scan the default Wine prefix for installed Windows plugin DLLs. All six paths are hidden directories excluded by the home interface. Only yabridgectl runs inside the snap; actual plugin hosting happens in the DAW’s process outside the snap. Without these paths, yabridge cannot perform its core function.
Furthermore, yabridge must be a snap in order to provide a specific version of WINE that works with the actual upstream application. This does not work with traditional packaging.
-
- personal-files:
Hello @Eickmeyer!
Given the justification provided, granting access to the requested files makes sense to me +1 (#voteFor). What do other @reviewers think?
Hey @Eickmeyer
Sorry for the delay in my response.
The requested interfaces are considered super-privileged and are only granted after publisher vetting. According to the policy, the snap publisher, to be vetted, must be a member of the application upstream or a trusted groups. Right now, only snapcrafters and canonical employees are considered trusted groups. Unless I understood it wrong, I think you don’t meet this criteria (please let me know if I’m wrong here).
I raised the issue that other groups (MOTU among others) should possibly be added to the trusted groups. I’ll be back as soon as we can discuss it.
Sorry for any inconvenience.