Yea, I don't see the upside to managing plugins in this fashion. Imagine the following scenario...
Over the course of the past year, you've cobbled together a dozen songs; each leveraging a particular plugin. Using this model, each of those now contain a copy of the plugin.
Now you want to update the plugin in order to benefit from a bug fix or new feature... whatever. You have to now hunt down and do the needful across each of these projects. It just doesn't scale at all; especially when we expand this thought exercise to a dozen or more plugins. You'd be better off automating your "centrally installed" plugins via something like Ansible, a shell script, or whatever.
bundling always seems fun but it ends up just sucking
Yea, I don't see the upside to managing plugins in this fashion. Imagine the following scenario...
Over the course of the past year, you've cobbled together a dozen songs; each leveraging a particular plugin. Using this model, each of those now contain a copy of the plugin.
Now you want to update the plugin in order to benefit from a bug fix or new feature... whatever. You have to now hunt down and do the needful across each of these projects. It just doesn't scale at all; especially when we expand this thought exercise to a dozen or more plugins. You'd be better off automating your "centrally installed" plugins via something like Ansible, a shell script, or whatever.
bundling always seems fun but it ends up just sucking