The Repair team is the first VCV Community team to launch. The goal is simple: For each open-source plugin in the Plugin Manager, help the developer by sending a pull request that makes it build against the latest master branch of Rack. If you are not quite familiar with GitHub and git, the procedure is the following.
- Make sure to
git checkout master and git pull the latest Rack source code, and build it.
- Pick your favorite plugin and click Fork on its GitHub page.
git clone the forked repo in your plugins/ folder.
- Inspect the code, and apply the changes mentioned in the Plugin API Updates Thread
- Update the form of the Makefile to follow the Template Makefile, including the
RACK_DIR which will be useful later.
- Try building it with
make -j$(nproc). If you changed everything correctly and it finally builds, make a commit with a message like "Updated to Rack 0.6 API", and git push.
- On your GitHub fork, click "Create Pull Request", and submit it back to the plugin developer.
- After the plugin developer accepts your pull request, you may delete your personal repository.
The Repair team is the first VCV Community team to launch. The goal is simple: For each open-source plugin in the Plugin Manager, help the developer by sending a pull request that makes it build against the latest
masterbranch of Rack. If you are not quite familiar with GitHub and git, the procedure is the following.git checkout masterandgit pullthe latest Rack source code, and build it.git clonethe forked repo in yourplugins/folder.RACK_DIRwhich will be useful later.make -j$(nproc). If you changed everything correctly and it finally builds, make a commit with a message like "Updated to Rack 0.6 API", andgit push.