# Workflow for local packages

**URL:** https://discourse.julialang.org/t/workflow-for-local-packages/562
**Category:** General Usage
**Tags:** question
**Created:** [November 25, 2016, 2:39pm UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562 "2016-11-25T14:39:24Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [November 25, 2016, 2:39pm UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562/1 "2016-11-25T14:39:24Z")

</div>

I am wondering what the best workflow is for packages which are developed and used locally (before they are published).

Currently, I create them with `PkgDev.generate`, they end up in `~/.julia/v0.5`, and then I keep working on them. However, whenever I `Pkg.update()`, I get quite a few messages along the lines of

```julia
WARNING: Package [...]: skipping update (dirty)...

```

I am wondering if I should do something differently, to tell `Pkg` that these cannot be updated, since they only exist locally.

---

<div class="post-metadata">

### Author: ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)
#### Post date: [November 25, 2016, 4:33pm UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562/2 "2016-11-25T16:33:39Z")

</div>

Hello colleague,

you get the same warning if you have local changes to published packages. If your local package is commited, then Pkg.update just proceeds with the INFO: Updating MyPackage master…

---

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [November 26, 2016, 11:43am UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562/3 "2016-11-26T11:43:40Z")

</div>

Thanks, I understand, but is there a way not to have this warning?

---

<div class="post-metadata">

### Author: ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)
#### Post date: [November 26, 2016, 11:50am UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562/4 "2016-11-26T11:50:04Z")

</div>

commit your changes?

---

<div class="post-metadata">

### Author: ![Balinus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/balinus/32/243_2.png) [@Balinus](https://discourse.julialang.org/u/Balinus)
#### Post date: [November 26, 2016, 2:47pm UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562/6 "2016-11-26T14:47:12Z")

</div>

Once your modules are ready to be published, you put them into the “main” julia package directory?

---

<div class="post-metadata">

### Author: ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)
#### Post date: [November 26, 2016, 3:17pm UTC](https://discourse.julialang.org/t/workflow-for-local-packages/562/7 "2016-11-26T15:17:14Z")

</div>

@Balinus:

> [@Tamas\_Papp](#):
>
> Currently, I create them with PkgDev.generate, they end up in ~/.julia/v0.5, and then I keep working on them.

For most setups ~/.julia/v0.5 is the “main”. Pkg.update just assumes to update all packages non-dirty.
