On Wed, Feb 28, 2024 at 2:39 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote:
> The llvm github repo appears to see a lot of churn on branches we're not > interested in and is in general huge and unreliable to clone. > > Switch to shallow clones to improve the user experience. > This reminded me of something I recently observed in a kirkstone build. I set the following in my local.conf: BB_GENERATE_MIRROR_TARBALLS = "1" BB_GENERATE_SHALLOW_TARBALLS = "1" BB_GIT_SHALLOW = "1" For the most part this worked as expected, but the llvm recipe ended up with both a shallow (157 MB) *AND* a full (6.4GB) git clone .tar.gz file in the downloads directory. It is always possible that I mixed something up, but I tried it twice, being careful to start from a completely empty build. Each time I was able to unpack the gitshallow and git2 LLVM bundles and convince myself that I was looking at the same thing when the "release/13.x" branch was checked out. ..Ch:W.. -- *"Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire*
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#197251): https://lists.openembedded.org/g/openembedded-core/message/197251 Mute This Topic: https://lists.openembedded.org/mt/104633560/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
