# Using \`~/.julia/dev\` for local packages in v0.7

**URL:** <https://discourse.julialang.org/t/using-julia-dev-for-local-packages-in-v0-7/11648>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [June 13, 2018, 2:18pm UTC](https://discourse.julialang.org/t/using-julia-dev-for-local-packages-in-v0-7/11648 "2018-06-13T14:18:29Z")\
**Posts on this page:** 2\
**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:** [June 13, 2018, 2:18pm UTC](https://discourse.julialang.org/t/using-julia-dev-for-local-packages-in-v0-7/11648/1 "2018-06-13T14:18:29Z")

</div>

I have some “local” packages, some of which are not even on Github, WIP. My current setup just has them in a directory which I put in `LOAD_PATH`; mainly so that they don’t mix with packages in `~/julia/v0.6`.

Now I want to use these both on `v0.6` and `v0.7`. Is it OK to just move (`mv`) my local packages to `~/.julia/dev`, and have something like

```julia
if VERSION < v"0.7-"
    push!(LOAD_PATH, expanduser("~/.julia/dev"))
end

```

in my startup file? This seems to work on both v0.6 and v0.7-, I just want to make sure that they won’t be overwritten or modified automatically there.

---

<div class="post-metadata">

**Author:** ![ExpandingMan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/expandingman/32/866_2.png) [@ExpandingMan](https://discourse.julialang.org/u/ExpandingMan)\
**Post date:** [June 13, 2018, 2:47pm UTC](https://discourse.julialang.org/t/using-julia-dev-for-local-packages-in-v0-7/11648/2 "2018-06-13T14:47:41Z")

</div>

I do things similarly, and I was also wondering what was the best way to add my local development packages to the environments `Project.toml`. If you put them in `dev` they’ll be in the load path, but you’d still need to add them to the `Project.toml`. Right now the only way I know of doing that would be to `generate` a new project with the same name and then replace it (which of course is a bad solution anyway because the uuid’s would be all messed up).