# Nested environments in package

**URL:** <https://discourse.julialang.org/t/nested-environments-in-package/33157>\
**Category:** General Usage\
**Created:** [January 9, 2020, 1:36pm UTC](https://discourse.julialang.org/t/nested-environments-in-package/33157 "2020-01-09T13:36:57Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ffevotte](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ffevotte/32/6587_2.png) [@ffevotte](https://discourse.julialang.org/u/ffevotte)\
**Post date:** [January 9, 2020, 5:10pm UTC](https://discourse.julialang.org/t/nested-environments-in-package/33157/5 "2020-01-09T17:10:47Z")

</div>

Also look at this related thread:

> [@Handling various types of dependencies](https://discourse.julialang.org/t/handling-various-types-of-dependencies/27850):
>
> (I apologize in advance for the very long post) As I use Julia for ever more complex and complete projects, I seem to run into the following problem, where a single “project” contains lots of related code, which will be used in different contexts to perform different tasks. (I’m speaking here of a “project” in the Github sense; from here on let’s imagine I’m speaking of a git repository, and reserve the words “package” and “project” to express the Julia concepts defined in the Pkg.jl documentat…

Some of the (sometimes prospective) solutions mentioned there might be of some interest to you:

- [stacked environments](https://discourse.julialang.org/t/handling-various-types-of-dependencies/27850/6) (but see the [concerns](https://discourse.julialang.org/t/handling-various-types-of-dependencies/27850/11) raised by such solutions)
- [Run.jl](https://github.com/tkf/Run.jl)
- [sub projects](https://github.com/JuliaLang/Pkg.jl/issues/1233)

---

_[View the full topic](https://discourse.julialang.org/t/nested-environments-in-package/33157)._