# 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:** 10

<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 10, 2019, 2:11pm UTC](https://discourse.julialang.org/t/developping-non-registered-packages-should-i-always-do-dev-package/32013/10 "2019-12-10T14:11:31Z")

</div>

> Yes, that’s true. I remember that there used to be a discussion about it but I can’t find it right now. (One argument is that the tag on github can be changed to point to a different commit, which hurts the reproducibility)

Maybe you were thinking of this thread?

> [@Pkg add 'at' or 'trackto' / @ or #](https://discourse.julialang.org/t/pkg-add-at-or-trackto-or/12270):
>
> I don’t want to disturb too much for the development of Pkg3. I know you are quite busy. Nevertheless, I find a bit misleading that @ is used to pin a tagged commit of the package but a SHA hash cannot be used instead of the tag. [Documentation: Pkg → Adding registered packages](https://docs.julialang.org/en/latest/stdlib/Pkg/#Adding-registered-packages-1). Indeed one can pin the commit by using # which is supposed to track what’s next to it. It makes sense for a branch. Does it make for a commit? Maybe I’m missing something. Besides, in the documentation seems that using…

---

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