Skip to content
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

Move google/nearby external submodule and gfps_service component to separate repo #284

Open
finger563 opened this issue Jul 8, 2024 · 1 comment
Assignees
Labels

Comments

@finger563
Copy link
Contributor

Is your feature request related to a problem?

Right now full / deep clone (recursing through all the submodules) takes a little while because the google/nearby repository is quite large / has a lot of submodules. We're actually not using much of what they've got there, and on top of it many users may not be wanting to use the gfps_service component.

Describe the solution you'd like.

Move gfps_service component to a separate repository and move the google/nearby (which is currently under espp/external/nearby) to be within that component's detail folder instead.

Describe alternatives you've considered.

Continuing to force people to fully download google/nearby just to use this repo?

Additional context.

No response

@finger563 finger563 self-assigned this Jul 8, 2024
@finger563
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant