Big git .pack file about openssl HOT 5 CLOSED

fair. I’ll think about it over the holidays

from openssl.

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

from openssl.

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

from openssl.

Hi, any updates on this?
Thank you.

from openssl.

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

from openssl.