# Removing manifest file for packages

**URL:** https://discourse.julialang.org/t/removing-manifest-file-for-packages/84690
**Category:** General Usage
**Created:** [July 23, 2022, 11:25pm UTC](https://discourse.julialang.org/t/removing-manifest-file-for-packages/84690 "2022-07-23T23:25:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![hros](https://avatars.discourse-cdn.com/v4/letter/h/97f17d/32.png) [@hros](https://discourse.julialang.org/u/hros)
#### Post date: [July 23, 2022, 11:25pm UTC](https://discourse.julialang.org/t/removing-manifest-file-for-packages/84690/1 "2022-07-23T23:25:28Z")

</div>

I have this issue discussed, e.g. [link](https://discourse.julialang.org/t/packages-that-contain-manifest-toml-files/35534)  
should I remove manifest files from my packages?

---

<div class="post-metadata">

### Author: ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)
#### Post date: [July 23, 2022, 11:53pm UTC](https://discourse.julialang.org/t/removing-manifest-file-for-packages/84690/2 "2022-07-23T23:53:11Z")

</div>

> [@hros](#):
>
> should I remove manifest files from my packages?

yes

---

<div class="post-metadata">

### Author: ![hros](https://avatars.discourse-cdn.com/v4/letter/h/97f17d/32.png) [@hros](https://discourse.julialang.org/u/hros)
#### Post date: [July 24, 2022, 12:01am UTC](https://discourse.julialang.org/t/removing-manifest-file-for-packages/84690/3 "2022-07-24T00:01:27Z")

</div>

Thanks  
will do

could you elaborate on the reason for doing so

---

<div class="post-metadata">

### Author: ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [July 24, 2022, 12:12am UTC](https://discourse.julialang.org/t/removing-manifest-file-for-packages/84690/4 "2022-07-24T00:12:25Z")

</div>

It really depends on what you want to do: testing your package with _only_ a specific set of dependencies, or try over time possibly new versions of the other packages in the environment?

I think that for the development of a package you want to actually test your package with different, newer (but still semver-compatible) versions of the dependencies, instead if you’re developing an application, or a pipeline, you want to use _only_ a specific set of packages, and make sure that it works reliably with your fixed environment. In the former case you keep only the project file, with compat bounds properly set, in the latter case you keep also the manifest file.
