Since working with Ruby 'Gems' and more recently, PHP Composer 'Packages' through my web development work I've been wondering if something similar could be done with Juce modules?
I.e. a simple command line interface together with a file to keep track of modules associated with the current project (equivalent to a Gemfile or composer.json). These would usually point to Git repositories, and allow the user to specify which version they want to be installed for their project. Since a module's repositirory would also contain it's dependancies, installing a module would automatically grab its dependant modules.
The reason I'm thinking about this now is that I'm extending dRowAudio's pitch detection functionality, and rather than merging my work back into his module repository via a pull request, it feels cleaner to create a small module that has the dRowAudio library as one of its dependancies.
I would propose following the exampe of Composer, using a central .json file to define associated modules for a project. In keeping with Juce funky naming conventions it could be called... Modulate :) so we would have a modulate.json file at the root of a project.