this is a follow up idea on Can Versions.toml point to git branch instead of fixed git commit?
concretely does the current registry already work with an empty Versions.toml file in the restricted situation of just adding one package which does not have any other dependency without a Versions.toml.
Lets say I have package a private A depending on private package B which has no further dependency.
Both i registered in my private registry, both having only an empty Version.toml file. Having the registry linnked to my current julia…
… I cannot do
] add A
because it searches for a version for B but cannot find any and fails
… however I can in fact do
] add B
which will install it from master from the respective git respository link defined in the Registry entry.
(after having B installed, I can also add A of course)
hence my proposal:
make it possible to resolve dependencies within a registry also when no version is defined in Versions.toml, defaulting to master branch of the defined git repository
- this would just mimick functionality which is already there as elaborated above
- it is obvious and explicit for everyone that indeed no version is ready to be installed, but that this is development
- the fallback to master of the linked repository is already the default and perfectly fits the usecase for (initial) development with no stable versions yet