Open patkenneally opened 1 month ago
Howdy @patkenneally , thanks for posting this issue and thoughts on this. Some quick thoughts and questions on my side:
dist3
folder, but the spice file would remain I assume and would not need to be downloaded again? I'm 99% sure the answer is yes reading up on this, but wanted to check
Describe your use case While useful, the git-lfs feature on github counts to the repo's cloning bandwidth. When the CI processes of the core repo and of forks of the repo, clone the repo, the bandwidth used by transferring the large bsp files adds up quickly. Instead, how about we remove these files from git-lfs, and instead download them once at build time using the CMake file(DOWNLOAD) feature. This would allow them to be downloaded once, and they would no longer impact github's git-lfs bandwidth quotas. I believe we should avoid using git-lfs (having been the person who motivated its use in the first place) due to the bandwidth considerations.
A secondary, and much less of a priority, this would absolve users of needing to configure and understand the basics of git-lfs, which has proven tricky on the odd occasion.
A negative to this proposition is that we have no control over what/where NAIF choose to put the bsp's overtime. An alternative might be to find some place (other than rely on NAIF's download links) to host the files for this project which doesn't have cost/bandwidth impacts.
Describe alternatives solutions you've considered None
Additional context None