# Problem adding SPICE dependency into a custom module

**URL:** <https://discourse.julialang.org/t/problem-adding-spice-dependency-into-a-custom-module/27711>\
**Category:** New to Julia\
**Tags:** package, module, package-manager\
**Created:** [August 19, 2019, 9:56am UTC](https://discourse.julialang.org/t/problem-adding-spice-dependency-into-a-custom-module/27711 "2019-08-19T09:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![doomphoenix-qxz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/doomphoenix-qxz/32/7009_2.png) [@doomphoenix-qxz](https://discourse.julialang.org/u/doomphoenix-qxz)\
**Post date:** [August 19, 2019, 4:54pm UTC](https://discourse.julialang.org/t/problem-adding-spice-dependency-into-a-custom-module/27711/2 "2019-08-19T16:54:12Z")

</div>

I think what you’re saying is that SPICE isn’t yet registered as a Julia package (meaning it doesn’t have an entry on the general registry such that `Pkg` knows what you mean if you just type `add SPICE`).

I’m not an expert in unregistered packages, and when I tried to do something like this I gave up and squashed everything into a single unregistered package that I `dev`’d and called via `using` in a script. But the following might help:

[https://discourse.julialang.org/t/pkg-workflow-for-unregistered-packages/17385](https://discourse.julialang.org/t/pkg-workflow-for-unregistered-packages/17385)

---

_[View the full topic](https://discourse.julialang.org/t/problem-adding-spice-dependency-into-a-custom-module/27711)._