https://bugs.kde.org/show_bug.cgi?id=410835
--- Comment #2 from Alexei Robyn <bugs....@shados.net> --- My intended use is packaging Falkon and third-party plugins separately. I'm looking at improving the packaging of Falkon in nixpkgs to account for third-party plugins, and the Nix approach to packaging stores individual packages in isolated FHS-like subtrees. Right now I have a kind of meta package that symlinks a set of plugins into a single directory, and wraps falkon to set $FALKON_PLUGIN_PATH to that directory of symlinks. If it were instead treated as a search path, I could just point it directly to the individual plugin directories, which would be preferable. On non-Nix-based distros, I could also see this being useful for allowing people to use plugins from both system and user sources. -- You are receiving this mail because: You are watching all bug changes.
