draw-things-community (and presumably other SwiftPM consumers) pins this repo via a raw commit revision:
.package(url: "https://github.com/liuliu/ccv.git", revision: "aaa3bf3d1b27e87622a14c1a91f099fb7e0eb73b")
SwiftPM's dependency resolution requires a full clone for revision:-pinned dependencies — it can't shallow-fetch an arbitrary commit the way it can a tagged version (from: "x.y.z"). In practice this means every fresh build fetches the entire history of this repo (tens of thousands of objects), which is slow and avoidable.
Would you be open to adding a single tag at the commit currently pinned (aaa3bf3d1b27e87622a14c1a91f099fb7e0eb73b)? That wouldn't require any code changes or an ongoing release process -- just one tag, so downstream consumers can switch to from:/.exact() and get shallow fetches. Since draw-things-community depends on this exact commit, it'd speed up builds of that project too.
Happy to open a PR against draw-things-community's Package.swift once/if a tag exists.
draw-things-community (and presumably other SwiftPM consumers) pins this repo via a raw commit revision:
SwiftPM's dependency resolution requires a full clone for
revision:-pinned dependencies — it can't shallow-fetch an arbitrary commit the way it can a tagged version (from: "x.y.z"). In practice this means every fresh build fetches the entire history of this repo (tens of thousands of objects), which is slow and avoidable.Would you be open to adding a single tag at the commit currently pinned (
aaa3bf3d1b27e87622a14c1a91f099fb7e0eb73b)? That wouldn't require any code changes or an ongoing release process -- just one tag, so downstream consumers can switch tofrom:/.exact()and get shallow fetches. Since draw-things-community depends on this exact commit, it'd speed up builds of that project too.Happy to open a PR against draw-things-community's Package.swift once/if a tag exists.