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

chore: use a lance fork without the duckdb submodule #2742

Merged
merged 2 commits into from
Mar 5, 2024

Conversation

universalmind303
Copy link
Contributor

lance uses duckdb as a submodule, and it's a pretty massive repo, 555.9 MB on a fresh clone. It currently takes absolutely forever to build glaredb the first time (or subsequent times if you nuke your cargo cache).

git clone https://github.com/duckdb/duckdb.git alone takes almost 4 minutes locally.

this just forks lance and removes the submodule to avoid the problem alltogether.

@universalmind303 universalmind303 enabled auto-merge (squash) March 5, 2024 20:52
@universalmind303 universalmind303 merged commit 9c27dd0 into main Mar 5, 2024
25 checks passed
@universalmind303 universalmind303 deleted the universalmind303/lance-fork branch March 5, 2024 20:52
tychoish pushed a commit that referenced this pull request Mar 6, 2024
lance uses duckdb as a submodule, and it's a pretty massive repo, `555.9
MB` on a fresh clone. It currently takes absolutely forever to build
glaredb the first time _(or subsequent times if you nuke your cargo
cache)_.

`git clone https://github.com/duckdb/duckdb.git` alone takes almost 4
minutes locally.

this just forks lance and removes the submodule to avoid the problem
alltogether.
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