No one with experience in Linux audio installs plugins from the OS repositories.
They're outdated.
They've suffered from the problems that come with it. The system decides to change library paths, and suddenly, you don't know where the plugins are. Administrative privileges make it difficult to solve the problem if you're not an experienced user (there have been issues with this in this very forum). Making backups becomes an unmanageable nightmare.
You don't want to deal with pre-installed plugins you'll never use, which make it difficult to find the ones you will (as is the case with themed Linux distributions for audio and multimedia).
They stopped working due to the abandonment of GTK2.
Installing plugins in the system directory is pointless because they aren't application dependency libraries; they're user utilities. The only justifiable case is if the plugin is truly an essential dependency for a program to perform a specific function (for example, GMsynth lv2, which includes Ardour by default).
But if you go to the developer's website, they distribute it as a zip file.
True, the paths to plugins installed in the administrative directory would be a jumble of dots and slashes, but they would work. Although, really, what musician installs their plugins there anymore? We all do it locally, for the reasons explained.
I've even managed to get Calf running locally and working.
My 4 cents (2 yours and 2 mine) :) I'm not trying to start an argument, just letting you know that it's a reality these days.
That's not true. Distributing plugins via installers is an outdated practice.
Users need control over where and how they organize their plugins. Control over whether or not they want to update.
How many of these are distributed as installers?
https://linuxdaw.org/?p=f&l=o
No one with experience in Linux audio installs plugins from the OS repositories.
They're outdated.
They've suffered from the problems that come with it. The system decides to change library paths, and suddenly, you don't know where the plugins are. Administrative privileges make it difficult to solve the problem if you're not an experienced user (there have been issues with this in this very forum). Making backups becomes an unmanageable nightmare.
You don't want to deal with pre-installed plugins you'll never use, which make it difficult to find the ones you will (as is the case with themed Linux distributions for audio and multimedia).
They stopped working due to the abandonment of GTK2.
Installing plugins in the system directory is pointless because they aren't application dependency libraries; they're user utilities. The only justifiable case is if the plugin is truly an essential dependency for a program to perform a specific function (for example, GMsynth lv2, which includes Ardour by default).
But if you go to the developer's website, they distribute it as a zip file.
https://x42-plugins.com/x42/x42-gmsynth
True, the paths to plugins installed in the administrative directory would be a jumble of dots and slashes, but they would work. Although, really, what musician installs their plugins there anymore? We all do it locally, for the reasons explained.
I've even managed to get Calf running locally and working.
My 4 cents (2 yours and 2 mine) :) I'm not trying to start an argument, just letting you know that it's a reality these days.