# Additional packages in Pkg3

**URL:** <https://discourse.julialang.org/t/additional-packages-in-pkg3/11632>\
**Category:** General Usage\
**Tags:** pkg\
**Created:** [June 13, 2018, 2:30am UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632 "2018-06-13T02:30:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![amrods](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/amrods/32/2543_2.png) [@amrods](https://discourse.julialang.org/u/amrods)\
**Post date:** [June 13, 2018, 2:30am UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/1 "2018-06-13T02:30:52Z")

</div>

Is there a way to list “additional packages” in 0.7?

In 0.6 one could do `Pkg.status()` and get a list of all installed packages, including those installed as requirements for `add`ed packages, whereas in 0.7 `status` only prints the `add`ed packages.

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [June 13, 2018, 3:06am UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/2 "2018-06-13T03:06:40Z")

</div>

You can look at the manifest and that file will give you all packages installed for your project. It will handle the dependency chaos and have all packages that are needed/installed.

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [June 13, 2018, 5:49am UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/3 "2018-06-13T05:49:35Z")

</div>

I think the new package manager looks great.  
For my understanding:  
If I open a new julia session and type “using MyPackage” julia will look up the manifest.toml in the folder MyPackage.jl and load exactly these dependencies (in the specified version and branches), right?

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [June 13, 2018, 8:34am UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/4 "2018-06-13T08:34:48Z")

</div>

> [@bernhard](#):
>
> If I open a new julia session and type “using MyPackage” julia will look up the manifest.toml in the folder MyPackage.jl and load exactly these dependencies (in the specified version and branches), right?

No, it will look in the Manifest of the current environment (the path to that manifest is shown when you e.g. do `pkg> st`.). Manifests in package folder are not used unless that is your current environment.

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [June 13, 2018, 9:07am UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/5 "2018-06-13T09:07:51Z")

</div>

thank you.  
I can see that cd() will change the ‘active’ environment if needed.

---

<div class="post-metadata">

**Author:** ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)\
**Post date:** [June 13, 2018, 12:21pm UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/6 "2018-06-13T12:21:56Z")

</div>

That bit actually concerns me, for security reasons (same reason that you’re not supposed to put `.` in your executable path).

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [June 13, 2018, 12:23pm UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/7 "2018-06-13T12:23:21Z")

</div>

[https://github.com/JuliaLang/Pkg.jl/issues/360](https://github.com/JuliaLang/Pkg.jl/issues/360)

[https://github.com/JuliaLang/julia/issues/27411](https://github.com/JuliaLang/julia/issues/27411)

---

<div class="post-metadata">

**Author:** ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)\
**Post date:** [June 13, 2018, 12:45pm UTC](https://discourse.julialang.org/t/additional-packages-in-pkg3/11632/8 "2018-06-13T12:45:19Z")

</div>

OK, I like the idea of a “Pkg.cwe” (bikeshedding needed!) function (and “cwe …” REPL command) to explicitly set the working environment, less like to break things if somebody is just doing a `cd` because of needing to run some OS commands in that directory, etc.)