Skip to content

Conversation

RobLoach
Copy link
Contributor

@RobLoach RobLoach commented Mar 22, 2020

Using the 3rd-party submodule has caused some problems when updating dependencies. While the idea is sound, it makes synchronising vendor code difficult. You have to update the 3rd-party repository, and then update the TIC-80 submodule to reference the fork.

This change splits the 3rd-party submodule into individual submodules in the vendor directory. The same code is checked out, so there isn't any change in how TIC-80 functions. All this does is makes updating third-party vendor code easier since you can then just update it in one place.

@RobLoach RobLoach changed the title Replace 3rd-party submodule tree with vendor directory Split up 3rd-party submodule into individual vendor submodules Mar 22, 2020
Copy link
Owner

@nesbox nesbox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, it was expected :)
thank you
also, I think, we have to mention all these submodules in the readme

@nesbox nesbox merged commit 74511cd into nesbox:master Mar 23, 2020
@nesbox nesbox added this to the 0.80.0 milestone Mar 23, 2020
@RobLoach
Copy link
Contributor Author

also, I think, we have to mention all these submodules in the readme

Agreed. There is docs to run git clone --recursive, but have a specific call out is a great idea.

@RobLoach
Copy link
Contributor Author

Also, thanks! I can completely understand its use and purpose. Just added a little bit of complexity. Hopefully taking this approach we don't lose out on some of the 3rd-party repo benefits.

@nesbox nesbox removed this from the 0.80.0 milestone Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants