# Enforcing dependencies in my own package

**URL:** <https://discourse.julialang.org/t/enforcing-dependencies-in-my-own-package/16967>\
**Category:** General Usage\
**Created:** [October 30, 2018, 1:14pm UTC](https://discourse.julialang.org/t/enforcing-dependencies-in-my-own-package/16967 "2018-10-30T13:14:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [October 30, 2018, 1:33pm UTC](https://discourse.julialang.org/t/enforcing-dependencies-in-my-own-package/16967/3 "2018-10-30T13:33:52Z")

</div>

> [@fredrikekre](#):
>
> The `Manifest.toml` file in the package is not used at all (this is the most common misconception about how Pkg works)

did this change? cf

> [@Does Manifest.toml belong in the repository?](https://discourse.julialang.org/t/does-manifest-toml-belong-in-the-repository/12029/3):
>
> It might also be nice to have a manifest checked into package repos for a few reasons: So that you have at least one known good configuration that presumably passed tests and such. To keep the different developers of the package in sync using similar setups. Of course, 2 cuts both ways: it’s nice that all the devs have similar setups and they can upgrade in sync, but that means that there’s less testing of the package with different setups. Benefit 1 may be better accomplished with some kind …

---

_[View the full topic](https://discourse.julialang.org/t/enforcing-dependencies-in-my-own-package/16967)._