# Best practice for academic code reproducibility (Manifest.toml between versions of julia)

**URL:** <https://discourse.julialang.org/t/best-practice-for-academic-code-reproducibility-manifest-toml-between-versions-of-julia/78307>\
**Category:** Package Management\
**Tags:** reproducibility\
**Created:** [March 22, 2022, 10:05pm UTC](https://discourse.julialang.org/t/best-practice-for-academic-code-reproducibility-manifest-toml-between-versions-of-julia/78307 "2022-03-22T22:05:36Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![feanor12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/feanor12/32/8212_2.png) [@feanor12](https://discourse.julialang.org/u/feanor12)\
**Post date:** [March 23, 2022, 7:34pm UTC](https://discourse.julialang.org/t/best-practice-for-academic-code-reproducibility-manifest-toml-between-versions-of-julia/78307/5 "2022-03-23T19:34:26Z")

</div>

What I did to enable easy reproducibility was to add a shell script that downloads a specific Julia version in a local folder, setup the correct path, instantiates the current project and runs the program I want to ship.  
This allows for a relative small archive to be shipped that can be run by others.

Just make sure to include some checks to avoid downloading Julia every time. 😉

---

_[View the full topic](https://discourse.julialang.org/t/best-practice-for-academic-code-reproducibility-manifest-toml-between-versions-of-julia/78307)._