thanks a lot. I was really sure this was because of a dependency, but then I probably haven’t looked detailed enough. (the dependency problem was the major problem I had before locally, because of Automatically detect unregistered dependencies by 00vareladavid · Pull Request #1088 · JuliaLang/Pkg.jl · GitHub. This topic here occured when wanting to jump between machines. Apparently this got me confused). I hope I find time soon to check this again on my system.
EDIT: I found the difference. I directly installed the package using ] dev instead of ] add. I tried it with your Staging area, and could successfully run ] dev JuAFEM after adding the registry.
Still I think it is very valuable to have this fallback feature in the Registry. Reasons:
-
it simplifies the initial phase when developing new packages a lot
-
it does not bind versions to branches (as disliked in another discourse discussion), but only has a fallback branch when no version is given
-
with it the registry is the one central place where you can register all your packages in development
For comparison: The pull request Automatically detect unregistered dependencies by 00vareladavid · Pull Request #1088 · JuliaLang/Pkg.jl · GitHub only works with Manifest-files within each of the packages to be installed. Hence you have to curate the manifest files for all packages independently. Which is especially cumbersome because this stage development you are constantly working with
] develop ...installations, which will alter your manifest file. -
when using a registry today for this purpose, you artificially have to bind a git commit tree-hash to a thought-up version number, while there is in fact no stable version yet to use at this stage of development. This would no longer be needed, as the Versions.toml could stay empty