Very nice! Thank you! It won't load until obs updated to the commit with OBS_PLUGINS*_PATHvariables support [fn:1], but as you said it's future-proof and alreadyinstalls to the correct location. There is another very similar patch, which adds another obs plugin. Youprobably already aware of it, but here is a link:http://issues.guix.gnu.org/45961.Accidentally, it has empty propagatedinputs and I'm not sure if it will apply to current master at all, but Ican update it if it's needed.
Toggle quote (15 lines)> It won't load until obs updated to the commit with OBS_PLUGINS*_PATH> variables support [fn:1], but as you said it's future-proof and already> installs to the correct location.>> There is another very similar patch, which adds another obs plugin. You> probably already aware of it, but here is a link:> http://issues.guix.gnu.org/45961. Accidentally, it has empty propagated> inputs and I'm not sure if it will apply to current master at all, but I> can update it if it's needed.>>> * Footnotes>> [fn:1] http://issues.guix.gnu.org/46113
Ah ha! So on ‘master’, there’s the OBS_PLUGINS_DIRECTORY patch that youprovided earlier, which is why I wrote that the plugins should work. Should we wait for the next OBS release instead of packaging anarbitrary commit? Ludo’.
Hi, Thanks for merging my patch =) I am not insist on keeping , but I do think that is more cleaner solution. With the upstream patch, Obs will be able to extend the list of plugin directories. We are going to add ~/.guix-profile/ to that list, which means Obs will have two different locations with partially different so files. It doesn't look clean to me. In addition,  doesn't require to have OBS_PLUGINS_DIRECTORY variables. If there is no such, it will run with its defaults.