# Distributing scripts with self-managed dependencies

**URL:** <https://discourse.julialang.org/t/distributing-scripts-with-self-managed-dependencies/102317>\
**Category:** Package Management\
**Created:** [July 31, 2023, 4:06pm UTC](https://discourse.julialang.org/t/distributing-scripts-with-self-managed-dependencies/102317 "2023-07-31T16:06:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [July 31, 2023, 9:58pm UTC](https://discourse.julialang.org/t/distributing-scripts-with-self-managed-dependencies/102317/4 "2023-07-31T21:58:57Z")

</div>

> [@bensetterholm](#):
>
> (I am using `dev` instead of `add` since I could not figure out an easy way to get Pkg to remember our Gitlab ssh key, and having to enter this in each time to update the module is too much of a pain)

I don´t know what’s about that ssh key, but if you make your code a proper package, you will just tell the users to “add” the package and that will the care of all dependencies, with proper versions, etc.

(absolutely tell them to install julia with juliaup).

This is one way to have scripts working with minimal startup time: [Creating a standalone app on different platforms - #3 by lmiq](https://discourse.julialang.org/t/creating-a-standalone-app-on-different-platforms/102089/3)

---

_[View the full topic](https://discourse.julialang.org/t/distributing-scripts-with-self-managed-dependencies/102317)._