Locate and purge old Godot binaries from LFS to reduce repository size #142

Open
opened 2022-01-05 19:44:29 +01:00 by unfa · 6 comments

Most of teh current respoistory size is due to the necessity of bunndling Godot editor binaries fro various platforms. this is due to the pre-alpha status of Godot 4 and the need to somehow keep the team using a single version of Godot.

There's gigabytes of old, unneeded Godot binaries in the repo that can and should be purged.

I just don't know how to do this.
If we could grep, deleting godot*.zip, godot*.dmg and *.tpz would be enough.

Of course we'd need to be careful not to delete the currently used versions. But we could probably purge all and then commit a new versions righ away.

Anybody knows how to do this?

Most of teh current respoistory size is due to the necessity of bunndling Godot editor binaries fro various platforms. this is due to the pre-alpha status of Godot 4 and the need to somehow keep the team using a single version of Godot. There's gigabytes of old, unneeded Godot binaries in the repo that can and should be purged. I just don't know how to do this. If we could grep, deleting `godot*.zip`, `godot*.dmg` and `*.tpz` would be enough. Of course we'd need to be careful not to delete the currently used versions. But we could probably purge all and then commit a new versions righ away. Anybody knows how to do this?
Does this help? https://stackoverflow.com/a/34582910/2611995

There's gigabytes of old, unneeded Godot binaries in the repo that can and should be purged.

I'm a little confused as to why this would be the case. Git LFS supposedly just stores pointers to the data; those gigabytes of old Godot binaries would only get downloaded if you checked out the revision in which they were used, at which point they'd need to get fetched from this server.

Are the Godot binaries not tracked with LFS?

> There's gigabytes of old, unneeded Godot binaries in the repo that can and should be purged. I'm a little confused as to why this would be the case. Git LFS supposedly just stores pointers to the data; those gigabytes of old Godot binaries would only get downloaded if you checked out the revision in which they were used, at which point they'd need to get fetched from this server. Are the Godot binaries not tracked with LFS?

Could it be you forgot to run git lfs prune @unfa before making your repository snapshot tarball? That could possibly explain why the tarball is so big.

Unless you made the snapshot by clicking "download the repository" in the web UI, in which case, yeah it'd have to include everything.

Could it be you forgot to run [`git lfs prune`](https://www.mankier.com/1/git-lfs-prune) @unfa before making your repository snapshot tarball? That could possibly explain why the tarball is so big. Unless you made the snapshot by clicking "download the repository" in the web UI, in which case, yeah it'd have to include everything.
Poster
Owner

@bepzi This issue is about reducing the size of the repository on the server, not about issues on users end.

Yes, these fiels are tracked by LFS and yes - it does store poiners in git. Users should only need to access the latest Godot editor binaries, unless we want to test against engine regressions (that actually could be very useful).

Hmm. Maybe we shouldn't clean that up just yet then...

@bepzi This issue is about reducing the size of the repository on the server, not about issues on users end. Yes, these fiels are tracked by LFS and yes - it does store poiners in git. Users should only need to access the latest Godot editor binaries, unless we want to test against engine regressions (that actually could be very useful). Hmm. Maybe we shouldn't clean that up just yet then...
Poster
Owner

It turns out ther exists a public archive of Gotod 4 dev builds:
https://downloads.tuxfamily.org/godotengine/testing/4.0/

We can purge Godot binaries form the repository entirely and shift to using this instead.

It turns out ther exists a public archive of Gotod 4 dev builds: https://downloads.tuxfamily.org/godotengine/testing/4.0/ We can purge Godot binaries form the repository entirely and shift to using this instead.
Poster
Owner

Could it be you forgot to run git lfs prune @unfa before making your repository snapshot tarball? That could possibly explain why the tarball is so big.

That is true. I did not know about this and did not do that. Very good point!

> Could it be you forgot to run [`git lfs prune`](https://www.mankier.com/1/git-lfs-prune) @unfa before making your repository snapshot tarball? That could possibly explain why the tarball is so big. That is true. I did not know about this and did not do that. Very good point!
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: unfa/liblast#142
There is no content yet.