Closed vlasty-proglove closed 7 months ago
fair. I’ll think about it over the holidays
Hi, any updates on this? Thank you.
There are many problems. With SwiftPM's current state, it has to be a separate repository, or any attempt to rewrite history to make it lighter will break current users. The actual improvement would be if SwiftPM used shallow clone. That's not a priority last time I checked
Already reported as #107 and #156
I'm totally in for separating the build results repository and the scripts (#156). Even at the cost of breaking existing uses, it's a one-time change that will likely be solved with changing the URL and the version of the dependency for the end-user.
Given how often an SPM cache clean is needed when working with the large projects, this would be a welcome change.
Shallow clone would have solved it though: https://stackoverflow.com/questions/69944121/swift-package-manager-shallow-clone
Now you can update your setup to use https://github.com/krzyzanowskim/OpenSSL-Package that is a drop-in replacement URL for the same package
Hi and thank you for your contribution.
At the moment, Xcode SPM does not filter the package but downloads the whole repository. The file in your .git/objects/pack folder with extension .pack is almost 1gb.
Can OpenSSL.xcframework be hosted on a different repo that will be used to just download the Framework?
Thank you.