# Pkg(3): develop package which depends on local/unregistered package

**URL:** <https://discourse.julialang.org/t/pkg-3-develop-package-which-depends-on-local-unregistered-package/12164>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [July 4, 2018, 2:42pm UTC](https://discourse.julialang.org/t/pkg-3-develop-package-which-depends-on-local-unregistered-package/12164 "2018-07-04T14:42:54Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![ianfiske](https://avatars.discourse-cdn.com/v4/letter/i/58f4c7/32.png) [@ianfiske](https://discourse.julialang.org/u/ianfiske)\
**Post date:** [August 6, 2018, 8:24pm UTC](https://discourse.julialang.org/t/pkg-3-develop-package-which-depends-on-local-unregistered-package/12164/24 "2018-08-06T20:24:26Z")

</div>

This doesn’t answer my exact question above, but following [[ANN] Introducing Upgradathon Fridays - #3 by fredrikekre](https://discourse.julialang.org/t/ann-introducing-upgradathon-fridays/12047/3) is working better for me. To start upgrading a [private] 0.6 package to 0.7 directly, I use `develop` on the remote git repo URL and then start working on the upgrade in my `~/.julia/dev/` directory.

---

_[View the full topic](https://discourse.julialang.org/t/pkg-3-develop-package-which-depends-on-local-unregistered-package/12164)._