5 ms·
Hey Flynn team, quick question: I noticed that in the past, flynn dependencies like slugbuilder/slugrunner were separate git repos. Some time ago, everything wa
by mikexstudios 12y ago
Hey Flynn team, quick question: I noticed that in the past, flynn dependencies like slugbuilder/slugrunner were separate git repos. Some time ago, everything was merged into the single flynn repo. What is the reasoning behind this move?
I see it as a disadvantage for other developers wanting to build on top of individual components. It also makes issues noisy.
- AYBABTME 12y agoNot on the Flynn team, but having a single repository instead of many makes it easier to make changes that cross packages without having to worry if you broke some remote thing. Here's an article that discusses this idea: https://www.digitalocean.com/company/blog/taming-your-go-dependencies/ https://www.digitalocean.com/company/blog/taming-your-go-dep...
- Titanous 12y agoHey, Flynn cofounder here. We merged the repos (there were a few dozen!) after encountering a ton of friction landing project-wide changes and managing the build system (vendoring dependencies in every repo got ridiculous). Contributors were also having a lot of trouble figuring out where to report issues and submit patches. On the whole the unified repo and build system has been a massive improvement to our productivity and the quality of the project. Unfortunately using components in a modular fashion can be harder, and we haven't come up with a great solution to that. We're still committed to keeping our components independently useful and would love to get feedback on what we can do better.
- mikexstudios 12y agoOkay, that makes sense. Thanks for the response!