# Manage dependencies to unofficial packages

**URL:** <https://discourse.julialang.org/t/manage-dependencies-to-unofficial-packages/26129>\
**Category:** New to Julia\
**Created:** [July 8, 2019, 7:28am UTC](https://discourse.julialang.org/t/manage-dependencies-to-unofficial-packages/26129 "2019-07-08T07:28:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DrChainsaw](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/drchainsaw/32/8497_2.png) [@DrChainsaw](https://discourse.julialang.org/u/DrChainsaw)\
**Post date:** [July 8, 2019, 11:05pm UTC](https://discourse.julialang.org/t/manage-dependencies-to-unofficial-packages/26129/2 "2019-07-08T23:05:36Z")

</div>

I think I found the answer:

> [@Pkg workflow for unregistered packages](https://discourse.julialang.org/t/pkg-workflow-for-unregistered-packages/17385):
>
> Hi, We have upgraded our projects/packages to Julia 1.0. The new Pkg is a well thought-out package manager, and we are currently trying to figure how to best use it in our development workflow. In the following, I describe our scenario first, then explain what workflow we currently have in mind, followed by some questions. Scenario: We develop an Application Bench, and two unregistered packages Foo and Bar. All three repositories live on github. Foo has a dependency on Bar. Both packages Foo…

I used the wrong terminology when searching (“unofficial” instead of “unregistered”) but after re-reading the pkg documentation I got it right.

I opted for adding a before\_install script to CI like this:  
julia -e ‘using Pkg; Pkg.add(PackageSpec(url=“[GitHub - DrChainsaw/NaiveNASlib.jl: Relentless mutation!!](https://github.com/DrChainsaw/NaiveNASlib.jl)”));’

---

_[View the full topic](https://discourse.julialang.org/t/manage-dependencies-to-unofficial-packages/26129)._