Re: [Nix-dev] handling /usr/lib/foo-plugins

2012-05-15 Thread Sergey Mironov
Thanks, I've looked under the zathura's hood - it uses following scheme: 1) gui part - zathura - is a core component, it should be compiled first 2) each plugin needs zathura to be built, but user may set target directory to put .so into (/usr/lib/zathura obtained from pkgconfig by default). 3)

Re: [Nix-dev] handling /usr/lib/foo-plugins

2012-05-11 Thread Yury G. Kudryashov
Sergey Mironov wrote: Hello list. I've tried to update zathura viewer (http://pwmt.org/projects/zathura/) from 0.01 to 0.1.2 but discovered that it is not that easy. Upstream developers decided to split the project into a GUI and a set of .so libraries (plugins for pdf- djvu- ps- etc). Those

Re: [Nix-dev] handling /usr/lib/foo-plugins

2012-05-11 Thread Marc Weber
The most simple way would be patching it to find its library in PATHs relative to PATH. Then it would not matter where the .so libraries are installed (system wide or user only). However if the plugin versions don't match the viewer version you'll be in trouble. That's why the alternative wrapper

[Nix-dev] handling /usr/lib/foo-plugins

2012-05-10 Thread Sergey Mironov
Hello list. I've tried to update zathura viewer (http://pwmt.org/projects/zathura/) from 0.01 to 0.1.2 but discovered that it is not that easy. Upstream developers decided to split the project into a GUI and a set of .so libraries (plugins for pdf- djvu- ps- etc). Those libraries are to be located