# Strategies to trim shipped not critical libs

**URL:** <https://discourse.julialang.org/t/strategies-to-trim-shipped-not-critical-libs/3657>\
**Category:** Internals & Design\
**Created:** [May 11, 2017, 8:54pm UTC](https://discourse.julialang.org/t/strategies-to-trim-shipped-not-critical-libs/3657 "2017-05-11T20:54:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/musm/32/3675_2.png) [@musm](https://discourse.julialang.org/u/musm)\
**Post date:** [May 11, 2017, 8:54pm UTC](https://discourse.julialang.org/t/strategies-to-trim-shipped-not-critical-libs/3657/1 "2017-05-11T20:54:03Z")

</div>

If you look at the Julia bin directory it includes several packages that are only used for convenience by other packages, in particular 7z and libexpat to name the ones I see as candidates. I’m wondering if it would be better to try to decouple shipping these libs from julia in favor of having them e.g. downloaded as needed from e.g. some separate package, or some similar strategy. I’m not exactly sure how things would look but wanted to bring up the discussion as I think it’s important as Julia tries to trim down.

---

<div class="post-metadata">

**Author:** ![mauro3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mauro3/32/292_2.png) [@mauro3](https://discourse.julialang.org/u/mauro3)\
**Post date:** [May 12, 2017, 7:38am UTC](https://discourse.julialang.org/t/strategies-to-trim-shipped-not-critical-libs/3657/2 "2017-05-12T07:38:39Z")

</div>

Are below issues addressing your concern?

[https://github.com/JuliaLang/julia/issues/5155](https://github.com/JuliaLang/julia/issues/5155)

[https://github.com/JuliaLang/julia/issues/18795](https://github.com/JuliaLang/julia/issues/18795)
