for creating one’s own registry one has to specify Versions.toml for each package currently it seems like you have to link versions to concrete git commits via hash, however for development it would be very helpful to link to branches instead. Is this already possible? can this be enabled?

true, however I for developing in a shared environment (cross OS, cross Machine, cross user) a registry is useful for sharing in the registry I need to specify versions for things to work at all, even if I don’t have any stable version yet. It would be super natural to instead point the registry …

Thats why you can add by a branch, then $ pkg update will automatically follow that branch. The purpose of the registry is to hold information about releases, not floating targets like a branch.

Might be cool to allow instantiating a manifest with dev’d packages and let it automatically check them out on the indicated branch. Agree that putting branches in the registry is not the way to go.

Yea, that is basically Automatically detect unregistered dependencies by 00vareladavid · Pull Request #1088 · JuliaLang/Pkg.jl · GitHub . Another thing that I have used a bit is to include the package in a registry, without any versions. That at least allows for e.g. $ pkg add UnregisteredPackage#br…

Okay, now that https://github.com/JuliaLang/Pkg.jl/issues/1005 is going to be solved things look different. Still there is the following problem: when relying on a manifest file to share the dependencies, it should stay somehow fixed for every package still I want to develop certain packages, hen…

I tried having a registry without any versions, however this failed immediately for adding packages which have other private packages in their dependencies (something like “no suitable version could be found for dependency …” was raised, which at least makes sense as no version is given) EDIT: this…

Can Versions.toml point to git branch instead of fixed git commit?

General Usage

StefanKarpinski January 16, 2020, 2:58pm 2

If you dev a package then it only needs the path, not anything else.

Topic		Replies	Views
Registry: support resolving dependencies also when Versions.toml file is empty by using master General Usage	4	580	January 25, 2020
Enforcing dependencies in my own package General Usage	9	1634	April 13, 2022
Package dependency to an unregistered version of a registered package General Usage package	2	482	December 3, 2020
More convenient way to develop dependent package? General Usage	8	590	February 11, 2022
Add registry from git-tree-sha1 for deterministic Docker builds Internals & Design docker , general-registry	2	104	December 12, 2025

Can Versions.toml point to git branch instead of fixed git commit?

Related topics