# Developping non registered packages: should I always do dev package?

**URL:** <https://discourse.julialang.org/t/developping-non-registered-packages-should-i-always-do-dev-package/32013>\
**Category:** General Usage\
**Tags:** pkg\
**Created:** [December 8, 2019, 2:28pm UTC](https://discourse.julialang.org/t/developping-non-registered-packages-should-i-always-do-dev-package/32013 "2019-12-08T14:28:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Olivier\_Merchiers](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/olivier_merchiers/32/4073_2.png) [@Olivier\_Merchiers](https://discourse.julialang.org/u/Olivier_Merchiers)\
**Post date:** [December 9, 2019, 9:22am UTC](https://discourse.julialang.org/t/developping-non-registered-packages-should-i-always-do-dev-package/32013/4 "2019-12-09T09:22:38Z")

</div>

Thanks a lot for your answers.

> For unregistered packages, I would suggest creating a registry and your colleagues only need to [add that registry](https://julialang.github.io/Pkg.jl/v1.1/registries/#Managing-registries-1). And you can find many other discussions [here](https://discourse.julialang.org/t/creating-a-registry/12094/14) and [on Registrator.jl](https://github.com/JuliaRegistries/Registrator.jl/issues/39)

I never looked into registries. I will see how hard that is.

> Yes, only local. Unless you commit and push your changes to github…

I’m sorry, I’m not sure if I fully understand. Can you give some more details?

> The tag info will appear in Manifest.toml but not Project.toml.

Yes indeed. I just saw that. But the tags in Manifest.toml seems to be stuck on 0.1.0.  
Somehow for my unregistered package I cannot do [https://github/omerchiers/MyPackage.jl@v0.2](https://github/omerchiers/MyPackage.jl@v0.2)  
I have to put the commit SHA1 even though I pushed my tags to github.

thanks again for your time.  
Olivier

---

_[View the full topic](https://discourse.julialang.org/t/developping-non-registered-packages-should-i-always-do-dev-package/32013)._
