-
Notifications
You must be signed in to change notification settings - Fork 26
Description
On Linux, package managers take care of where files are installed for which application (package) on a system-wide level.
Vim supports several plugin folders, that are tested, when it starts. One is system-wide (all users of a given system can use that plugin) and one is user-specific (only the user starting vim can use that plugin).
As I'm now maintaining supercollider for Arch Linux, I'd like to have a look into how to ship scvim as a plugin package (e.g. vim-scvim or vim-supercollider).
This has the above mentioned benefit of several users being able to use the same installation.
Starting from 3.9, scvim will most likely not be compiled by default (which has the benefit of being able to update scvim, while supercollider is not updated).
Also, to circumvent #27, I have disabled scvim in the updated build of 3.8.0 for Arch Linux.
For this to happen, several things (ideally) will have to be done though:
- start to version (tag) scvim
- install supercollider and scvim files system wide
- install binaries and link libraries (sc_dispatcher and start_pipe)
- extend initClass and startUp.add of SCVim.sc for a global install
- bake a package