# Vendoring opam package

**URL:** <https://discuss.ocaml.org/t/vendoring-opam-package/15784>\
**Category:** Ecosystem\
**Tags:** opam\
**Created:** [December 12, 2024, 8:45am UTC](https://discuss.ocaml.org/t/vendoring-opam-package/15784 "2024-12-12T08:45:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![orbitz](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/orbitz/32/110_2.png) [@orbitz](https://discuss.ocaml.org/u/orbitz)\
**Post date:** [December 12, 2024, 8:45am UTC](https://discuss.ocaml.org/t/vendoring-opam-package/15784/1 "2024-12-12T08:45:17Z")

</div>

I’m wondering if there is a way to vendor an opam package + deps such that the output is an opam repository + local copy of all the inputs + the package uses that copy as source for building. It’d be nice to just be able to run a program to get that.

In searching I found opam-bundle, but that seems to just produce a big tarball + package that builds everything, more like it’s a way to deploy things to get built rather than a development flow.

Thank you

---

<div class="post-metadata">

**Author:** ![UnixJunkie](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/unixjunkie/32/638_2.png) [@UnixJunkie](https://discuss.ocaml.org/u/UnixJunkie)\
**Post date:** [December 12, 2024, 9:47am UTC](https://discuss.ocaml.org/t/vendoring-opam-package/15784/2 "2024-12-12T09:47:12Z")

</div>

I have used opam-bundle.  
But, it is not failsafe.  
You do need to test the obtained “installer” works for a fresh user in the Linux distribution you are targeting.