# Can a module in a package itself be a package?

**URL:** <https://discourse.julialang.org/t/can-a-module-in-a-package-itself-be-a-package/113474>\
**Category:** General Usage\
**Created:** [April 24, 2024, 7:59pm UTC](https://discourse.julialang.org/t/can-a-module-in-a-package-itself-be-a-package/113474 "2024-04-24T19:59:19Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sadish-d](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sadish-d/32/48058_2.png) [@sadish-d](https://discourse.julialang.org/u/sadish-d)\
**Post date:** [April 26, 2024, 3:48am UTC](https://discourse.julialang.org/t/can-a-module-in-a-package-itself-be-a-package/113474/8 "2024-04-26T03:48:59Z")

</div>

I had a very specific question in mind, but I came across a few things that I’m going to just leave here in case someone else finds them useful.

Turns out there are decent people doing all sorts of wild things when it comes to nested packages. Looks like ModelParameters.jl does the inverse of what I mentioned, equivalent to putting PackageFull is in a subfolder of PackageCore: [GitHub - rafaqz/ModelParameters.jl: Easy, standardised parameter get/set for heterogeneous or nested immutable models.](https://github.com/rafaqz/ModelParameters.jl/tree/master)

Something I hadn’t thought of is how the folder structure is going to interact with repositories. One approach suggests having a Repo folder, where the packages are in their own subfolder, but then the repo has a Project.toml and Manifest.toml: [Feature request: scan subdirs for updated versions/projects · Issue #1874 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/issues/1874#issuecomment-653762205)

And more discussion here:

> [@Usage of subdirectories to store multiple packages in a single repo](https://discourse.julialang.org/t/usage-of-subdirectories-to-store-multiple-packages-in-a-single-repo/55534/11):
>
> Thanks for pointing that out. I was unaware that building local registries like this was a practical means of registering multiple packages simultaneously. At some point, I thought I saw either @GunnarFarneback or @fredrikekre suggest that an automated flow could eventually be developed to achieve simultaneous registration. I wonder if the methodology you just outlined is the goal, or merely a temporary stepping stone (looking at a roughly 1 year timeframe, I suppose). I noticed the SnoopComp…

I don’t know where I’ll land. Some paths are more well trodden than others and the approach of using include() does not seem to be one of them.

---

_[View the full topic](https://discourse.julialang.org/t/can-a-module-in-a-package-itself-be-a-package/113474)._