Git LFS Quota issues about visualrust HOT 5 OPEN

I'm thinking it may actually make sense for us to just remove MinGW from the package. While it's theoretically nice from a batteries included standpoint, but we don't include rustc (and for good reason IMO - you should be able to separately upgrade it via rustup etc.) - so why should we include racer (which may be tied to rustc versioning anyways, and can be installed/upgraded through cargo) or mingw (which has plenty of distribution channels of it's own that could be separately installed if you want gdb/gnu toolchain support)?

I'd want good messaging and instructions for if the user is missing components but I think it makes more sense to remove these outright than to worry about distribution mechanisms for them.

StrongNamer might remain a problem but it's a much smaller package...

from visualrust.

This should be resolved by now The quota should have refilled by now, although I'm keeping builds of my fork disabled for the moment.

from visualrust.

It looks like this remains a problem.

from visualrust.

From the options that you have mentioned, I think that enabling caching and/or switching to an external package manager is the most sensible thing, although I don't know exactly for what kind of files LFS is being used for at the moment. Please don't put things directly into the repository ... LFS exists for a reason.

Ideally we could get rid of some large files completely (i.e., no longer depend on them at all) by cleaning up some stuff. I'm not sure if we really need all of this.

from visualrust.

Ran git lfs ls-files to get a full list.

from visualrust.