# Distributing compiled elixir packages?

**URL:** <https://forum.elixirforum.com/t/distributing-compiled-elixir-packages/51681>\
**Category:** Discussions\
**Tags:** package, hex-packages\
**Created:** [November 9, 2022, 5:09pm UTC](https://forum.elixirforum.com/t/distributing-compiled-elixir-packages/51681 "2022-11-09T17:09:55Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![al2o3cr](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/al2o3cr/32/3457_2.png) [@al2o3cr](https://forum.elixirforum.com/u/al2o3cr)\
**Post date:** [November 9, 2022, 6:18pm UTC](https://forum.elixirforum.com/t/distributing-compiled-elixir-packages/51681/5 "2022-11-09T18:18:10Z")

</div>

> [@gmile](#):
>
> Btw, if this was (or is being) discussed / explored before or elsewhere

There’s some concurrent discussion in this thread, though with a different set of requirements:

> [@Creating precompile library](https://forum.elixirforum.com/t/creating-precompile-library/51661):
>
> How to create Elixir library contains compiled beams instead of source code?

* * *

> [@gmile](#):
>
> there are various strategies to improve the compilation speed there, though that’s not the point of this message

One of the “various strategies” is caching the built BEAM files after a `mix deps.compile` - if you compute the cache key based just on `mix.lock` (so that the cache can be used across CI builds that have the same deps) you can get essentially the same results as precompiled packages but without any of the portability / security / etc headaches.

---

_[View the full topic](https://forum.elixirforum.com/t/distributing-compiled-elixir-packages/51681)._