# How to register/update my package with some local packages

**URL:** https://discourse.julialang.org/t/how-to-register-update-my-package-with-some-local-packages/127912
**Category:** General Usage
**Tags:** package
**Created:** [April 10, 2025, 9:00am UTC](https://discourse.julialang.org/t/how-to-register-update-my-package-with-some-local-packages/127912 "2025-04-10T09:00:11Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)
#### Post date: [April 10, 2025, 1:40pm UTC](https://discourse.julialang.org/t/how-to-register-update-my-package-with-some-local-packages/127912/5 "2025-04-10T13:40:35Z")

</div>

I would recommend creating a GitHub Organization (maybe `JuliaHydroModels`) to host all these packages, instead of tying them to your personal user account. That way, you can have additional co-maintainers, and it’s not such a problem if you ever step back from the project.

Please make sure that every package has [at least](https://discourse.julialang.org/t/when-does-it-make-sense-to-post-a-new-package-to-the-julia-repository/108701/4) a README that explains the purpose of the package and how it relates to the main `HydroModels.jl`.

Assuming each package is ready for registrations, ~~you may want to consider manually preparing a Pull Request (with the help of [LocalRegistry package](https://github.com/GunnarFarneback/LocalRegistry.jl)) that registers _all_ of them in one go~~ (actually, don’t: [Gunnar’s suggestion](https://discourse.julialang.org/t/how-to-register-update-my-package-with-some-local-packages/127912/6) is a far better approach) . Otherwise, you have to deal with registering them in the order of their dependency graph, with a three-day period for each package.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-register-update-my-package-with-some-local-packages/127912)._