-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BeckstromResearch #513
Comments
Hey @chrisbeckstrom, I added this to the system, which means it'll be queued to build and send out through the plugin manager. However you should make a fix: you don't want to check your .o, .so and .dylib files into git...these should be built by whoever uses the code (like the build system for the plugin manager). Something like |
@chrisbeckstrom you also will need to remove those binaries from the HISTORY of the repository. See this link for more information on how to remove files from the repository history. |
Thanks @mdemanett and @cschol ! I think I have a lot to learn, thanks for helping me with this.
...means that at some point in the future, folks will be able to add my plugins via the plugin manager and have them automatically added to their plugins folder on their local machine? I.e. they won't have to build anything, the files will just appear and be ready to use |
Sorry, this is not quite enough yet, as the files are still in the HISTORY of the repository, i.e. I can check out an earlier revision of the repo and the files are back. See the steps in this issue chrisbeckstrom/Beckstrom_Research_Rack#7 to resolve it. |
It's not a huge issue because it's probably only a MB or two, but it does add up. We just don't want a recursive checkout to take up 20GB of space. |
Updated build |
plugin name: Beckstrom Research
slug name: BeckstromResearch
Repository: https://github.com/chrisbeckstrom/Beckstrom_Research_Rack
email address: chris@chrisbeckstrom.com
The text was updated successfully, but these errors were encountered: