Conversation
There was a problem hiding this comment.
(Oops, I deleted my comment.) Should there be an assert here to ensure that plugins are != null if wrapForGSTPlugins is true?
There was a problem hiding this comment.
i didn't add one, so that you can also choose to build quodlibet with just gst_plugins_base and w/o gst_plugins_{good,ugly}.
i could add an assert for at least one being available. shall i?
There was a problem hiding this comment.
If that's the intention I don't think an assert is needed. But I guess the "at least one" assert is kind of nice. You choose! :-)
|
@coroa: What is the purpose of the unwrapped variant? Don't you need gst plugins to play music? |
|
unwrapped variant works in nixos, and I'd say is preferable for nixos. wrapped |
|
@Phreedom: Why is the unwrapped preferred on nixos? Just so that you can add/remove gst plugins without rebuilding the app? (Just trying to understand.) |
|
@bjornfor: nixos takes care of adding gst_plugins_* to a global GST_PLUGIN_PATH environment variable. this way you can choose, which plugins are available by just adding them to your environment. |
|
I get eval error: Line 53 is I don't understand why nix sees the types as booleans, I thought they were packages/paths/strings. |
also provides two distinctive flavours, which either wrap the program to pull in the gstreamer plugins or not.
|
sorry, i'm at fault, for adding gst_plugins_bad and setting them to false in all-packages.nix instead of null. memo to self: always do a nix-build before pushing :P |
|
You can also do Pushed to master. Thanks! |
also provides two distinctive flavours, which either wrap the program to
pull in the gstreamer plugins or not.