Trying to get YAGSL working on our bot. I’m seeing a lot of changes to the YAGSL project itself, it’s not clear how those changes are getting propagated to the vendordep.
Is there a way to include the YAGSL source itself in our project (as a submodule), so we can take advantage of fixes, etc?
The dev branch has the swervelib folder which is a way to use YAGSL without the vendor library GitHub - BroncBotz3481/YAGSL-Example at dev
is that kept in sync with the main project?
The YAGSL Example Library is what we work out of. So the changes are made there first then propagated to the library GitHub
ok. so best practice is clone the example, make our own branch, and make sure we merge changes from the dev branch to ours periodically?
That’s up to you. I personally like that method. But I know @nstrike keeps the vendor lib updated.
I try to keep the vendordep up to date very often, the most it is ever out of date normally is ~3days. Whenever I add a new feature I also try to increment the number and i keep an updated changelog (starting this year) here.
You can absolutely include the dev branch of YAGSL-Example’s swervelib as a git submodule and periodically run git submodule update and it should work just fine if you want to live on the bleeding edge.
thanks for the confirmation. don’t want to live on the edge, but want the source there so we can get extra telemetry in to track down remaining problems…
if I have multiple development workstations that have had the vendordep added at different times, does this mean I could get different jar files depending on which version of the vendordep has been loaded on whichever workstation I happened to build on?
Vendordeps live with the project, so you should be synchronizing them along with the rest of your project’s code?
ah! didn’t realize the version number was wired into the vendordep. stupid question.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.