# Trouble with Pkg3

**URL:** <https://discourse.julialang.org/t/trouble-with-pkg3/11834>\
**Category:** Internals & Design\
**Created:** [June 20, 2018, 8:18pm UTC](https://discourse.julialang.org/t/trouble-with-pkg3/11834 "2018-06-20T20:18:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![00vareladavid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/00vareladavid/32/23521_2.png) [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)\
**Post date:** [June 20, 2018, 8:18pm UTC](https://discourse.julialang.org/t/trouble-with-pkg3/11834/1 "2018-06-20T20:18:15Z")

</div>

I’m trying to add support for a package which is still using the `REQUIRE` file. I’ve been following this [documentation](https://docs.julialang.org/en/latest/stdlib/Pkg/).

I added a `Project.toml` file. The `Project.toml` file has a line under `[deps]` which says `Compat = <somehash>`. But building the project (by running `add ./project_name`) fails with `Module Compat not found in the current path`. Running `using Compat` in the REPL does not return any errors.

I’m running Julia 0.7.0-alpha.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [June 20, 2018, 8:51pm UTC](https://discourse.julialang.org/t/trouble-with-pkg3/11834/2 "2018-06-20T20:51:38Z")

</div>

Could you be a bit more explicit on how the directory structure looks and where you run commands. If it is so detailed that it is easy to reproduce then it will be easier to see where things go wrong.

---

<div class="post-metadata">

**Author:** ![00vareladavid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/00vareladavid/32/23521_2.png) [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)\
**Post date:** [June 20, 2018, 9:17pm UTC](https://discourse.julialang.org/t/trouble-with-pkg3/11834/3 "2018-06-20T21:17:27Z")

</div>

Argh! I tracked down my error, I had not committed my changes before running `add ./project_name`. This is mentioned in the docs, but I must have missed it:

> The changes would have to be committed and the packages updated in order to pull in the changes.

In light of this, it seems like a good idea to add a warning when someone tries to `add` a local package that has not been commited? I can see myself making this same mistake again, even now that I’m aware of it.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [June 20, 2018, 9:31pm UTC](https://discourse.julialang.org/t/trouble-with-pkg3/11834/4 "2018-06-20T21:31:30Z")

</div>

Oh, I should have seen the `add` command. Yes, if you want direct usage of the files then you would use `dev`. Yeah, we could perhaps warn if `add`ing a dirty repo.

---

<div class="post-metadata">

**Author:** ![00vareladavid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/00vareladavid/32/23521_2.png) [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)\
**Post date:** [June 20, 2018, 9:39pm UTC](https://discourse.julialang.org/t/trouble-with-pkg3/11834/5 "2018-06-20T21:39:43Z")

</div>

Ok, that makes sense. I should have read the docs a little more thoroughly 😆. Thanks for the help!