# \#package-management

**URL:** https://discourse.julialang.org/tag/package-management/964.md

[Latest](https://discourse.julialang.org/latest.md) · [Categories](https://discourse.julialang.org/categories.md) · [Tags](https://discourse.julialang.org/tags.md)

---

## [Test package with dev-ed dependency](https://discourse.julialang.org/t/test-package-with-dev-ed-dependency/135740)

<div class="topic-metadata">

**Author:** [@nsajko](https://discourse.julialang.org/u/nsajko)\
**Replies:** 1\
**Last updated:** [February 20, 2026, 12:54am UTC](https://discourse.julialang.org/t/test-package-with-dev-ed-dependency/135740 "2026-02-20T00:54:50Z")

</div>

Package P depends on package D. I want to run the test suite of package P with a specific version of package D in the manifest. To be specific, I have D dev-ed, I want the dev-ed variant to be loaded for the test suite. …

---

## [\[ANN\] RegistryBrowser.jl - Interactively browse packages](https://discourse.julialang.org/t/ann-registrybrowser-jl-interactively-browse-packages/126802)

<div class="topic-metadata">

**Author:** [@GHTaarn](https://discourse.julialang.org/u/GHTaarn)\
**Replies:** 1\
**Last updated:** [March 27, 2025, 6:56am UTC](https://discourse.julialang.org/t/ann-registrybrowser-jl-interactively-browse-packages/126802 "2025-03-27T06:56:57Z")

</div>

For a long time I have wanted to be able to browse the packages in my registries directly from the REPL, so I built this tool to do this. The latest stable version is able to display all package information that is loca…

---

## [Migrate private registry to new server using LocalRegistry.jl](https://discourse.julialang.org/t/migrate-private-registry-to-new-server-using-localregistry-jl/100859)

<div class="topic-metadata">

**Author:** [@Christopher\_Fisher](https://discourse.julialang.org/u/Christopher_Fisher)\
**Replies:** 4\
**Last updated:** [June 27, 2023, 11:35am UTC](https://discourse.julialang.org/t/migrate-private-registry-to-new-server-using-localregistry-jl/100859 "2023-06-27T11:35:48Z")

</div>

Hi, I am using LocalRegistry.jl to manage a private package ecosystem. I need to move the registry and package ecosystem to a new server. How to I ensure that the registry and projects using the registry and package eco…

---

## [Different versions of same package in dependency graph](https://discourse.julialang.org/t/different-versions-of-same-package-in-dependency-graph/81895)

<div class="topic-metadata">

**Author:** [@HashBrown](https://discourse.julialang.org/u/HashBrown)\
**Replies:** 4\
**Last updated:** [May 30, 2022, 2:30pm UTC](https://discourse.julialang.org/t/different-versions-of-same-package-in-dependency-graph/81895 "2022-05-30T14:30:24Z")

</div>

Suppose I create a project environment and add packages P1@2.0.0 and P2@2.0.0. And lets say P1@2.0.0 depends on P2@1.0.0. Does this create a conflict (like it does in Python)? Or will Julia take care of this and use P2@2…

---

## [Collaborative development workflow for multiple packages simultaneously on multiple machines](https://discourse.julialang.org/t/collaborative-development-workflow-for-multiple-packages-simultaneously-on-multiple-machines/78942)

<div class="topic-metadata">

**Author:** [@claudio20497](https://discourse.julialang.org/u/claudio20497)\
**Replies:** 1\
**Last updated:** [April 4, 2022, 2:57pm UTC](https://discourse.julialang.org/t/collaborative-development-workflow-for-multiple-packages-simultaneously-on-multiple-machines/78942 "2022-04-04T14:57:28Z")

</div>

Hello, I’m simultaneously developing two packages, say mypkgA.jl and mypkgB.jl, where mypkgA.jl depends on mypkgB.jl. They’re both currently unregistered, and I have to work on two different machines depending on the da…

---

## [Opt-in \[compat\] tests ok ? augment ver list;](https://discourse.julialang.org/t/opt-in-compat-tests-ok-augment-ver-list/77048)

<div class="topic-metadata">

**Author:** [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)\
**Replies:** 5\
**Last updated:** [February 25, 2022, 2:51pm UTC](https://discourse.julialang.org/t/opt-in-compat-tests-ok-augment-ver-list/77048 "2022-02-25T14:51:46Z")

</div>

The introduction of a new version for a \[compat\] listed package results in nonempty status --outdated often enough that a safe opt-in way of reducing these events is desirable. To ensure the processing happen only if th…