# Pkg with LFS git extension

**URL:** <https://discourse.julialang.org/t/pkg-with-lfs-git-extension/16339>\
**Category:** Tooling\
**Tags:** package\
**Created:** [October 15, 2018, 10:55am UTC](https://discourse.julialang.org/t/pkg-with-lfs-git-extension/16339 "2018-10-15T10:55:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![phlavenk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/phlavenk/32/1873_2.png) [@phlavenk](https://discourse.julialang.org/u/phlavenk)\
**Post date:** [October 15, 2018, 10:55am UTC](https://discourse.julialang.org/t/pkg-with-lfs-git-extension/16339/1 "2018-10-15T10:55:36Z")

</div>

Hi, I’ve encountered problems with using LFS git extension when dev-ing package on Julia 1.0. is the large file extension supported by libgit2? is there any advice how to set-up it properly, or the general advice is to not use this feature at all? Thank’s a lot.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 15, 2018, 5:58pm UTC](https://discourse.julialang.org/t/pkg-with-lfs-git-extension/16339/2 "2018-10-15T17:58:11Z")

</div>

You can just use normal git to check something out and then when you dev it, Pkg will just use the already-checked-our version.

---

<div class="post-metadata">

**Author:** ![phlavenk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/phlavenk/32/1873_2.png) [@phlavenk](https://discourse.julialang.org/u/phlavenk)\
**Post date:** [October 16, 2018, 8:55am UTC](https://discourse.julialang.org/t/pkg-with-lfs-git-extension/16339/3 "2018-10-16T08:55:54Z")

</div>

Yeah, I though this will be the the right answer. Actually, the easy way is to not use LFS in Julia packages.  
What is the mechanism the BinaryBuilder uses to store binary dependencies on github? This might be also an option for my usecase.